P2P State versus Installment Plan State

[Former Member]

Hello Collections Experts,

Can someone explain the difference between the 'state of a Promise to Pay versus the state of an Installment Plan please? We cretaed a P2P as an installment plan. When we did this the state under tab 'Promise to Pay' column 'State of Promise To Pay' was recorded as 'Open'. If we click on Installment Plan the column 'State of Installment' was recorded as 'Open'. In table FDM_P2P_ATTR the state was recorded as 0 (Open) and in table UDM_P2P_ATTR the state was recorded as 0 (Open).

Later when the P2P was overdue, the state under tab 'Promise to Pay' column 'State of Promise To Pay' is showing as 'Installment is Overdue'. While under the Installment Plan itself the column 'State of Installment' is showing as 'Not Paid On Schedule'. In table FDM_P2P_ATTR  and table UDM_P2P_ATTR the state is recorded as 6 (Partially Kept Not On Schedule).

See attached.

We don't know why tab 'Promise to Pay' column 'State of Promise To Pay' is showing as 'Installment is Overdue' while the Installment Plan column 'State of Installment' is showing as 'Not Paid On Schedule'.

Are there different states for a P2P versus Installment plan and can anyone advise what DB tables these 2 seemingly different states are recorded/stored in?

Thanks and regards

Michael

[catherine_wade · Accepted solution]

Hi Michael

There are different states for the P2P and for the installment plan associated with it.  The program FDM_P2P_JUDGE evaluates both the P2P and and each installment and assigns the appropriate state to each one, for example you may have one installment that is paid in full & on time and another that has not been paid and the due date has passed, these would required different states, the P2P itself will have a different state.

If you go to table UDM_P2P_ATTR and do a dropdown on the field "FIN_P2P_STATE" you can see the list of states and their descriptions, these are the states that are applied by program FDM_P2P_JUDGE during evaluation, those with the word "schedule" will appy to the installment and the others will apply to the P2P, take a look at the attached for more information, regards

Evaluating Promises to Pay - SAP Collections Management (FIN-FSCM-COL) - SAP Library

[Former Member · Accepted solution]

Hello Catherine,

Thanks for the reply. I checked the table UDM_P2P_ATTR and can see the state there is 6 'Partially Kept Not on Schedule'. However, when I look in the UDM_SPECIALIST - Process Receivables screen itself, the state under P2P is 'Installment is Overdue' but under the installment itself the state is showing as 'Not Paid On Schedule'. Can you advise why one shows 'Installment is Overdue' but the other shows 'Not Paid On Schedule'? Is that text description of the state stored in separate tables given they have different texts?

Thank you for your help.

Michael

[catherine_wade · Accepted solution]

Hi Michael

It is the P2P state text that is different -'Partially Kept Not on Schedule' versus 'Installment is Overdue', I can't see any reference to - 'Installment is Overdue' in the FDM_P2P_JUDGE program so can I suggest you have the program run in debug to see where this text is getting allocated.