CRM system creates Sales Order with required Fileds and their update with all Follow up functions.
Comparing Sales Order schedule line data with CRM Order in CRM system to SCM system.
CRM Order Screen:
CRM system transaction CRMD_ORDER, show the values for the fields like Ordered Quantity, Confirmed Quantity, Delivered Quantity, Goods Issue quantity.
Service Fill/Service Loss Maintenance Monitor Screen
Transaction /n/sapapo/srvf_status- Service Fill/Service Loss Maintenance Monitor, enter the order and execute it, which displays below screen.
Service Fill/Service Loss Maintenance Monitor screen picks data from the table /SAPAPO/SRVFCSL.
To get detail level Log information, we need to set the field "Detail level for application log" in customizing APO -> Supply Chain Planning -> SPP -> Monitoring -> Service fill Monitor -> Make global settings for service fill monitor to "Save all messages".
The logging is for the transfer of data to SCM. If the logging is set to "Save all messages", all the data which is transferred from ERP/CRM to SCM is saved before it is processed on SCM side. So we have the possibility to analyze the data which comes into SCM.
In the provided example data the 0 values in the fields "Requirement Quantity" and "Confirmed Quantity" (tab "CRM data") seem to be correct. These are the values SCM receives from CRM.
On the tab "Result SF/SL" the values also seem to be correct: For example, the field "GI CustReqProd" should not display CRM data but field "GI CustReqProd" is a field which is calculated by the service fill analysis. Tab "Result SF/SL" shows the results of the service fill analysis, not imported data from CRM.
Trying to explain CRM order fields comparison with below screen shot.
Screen does not show the values for the fields Like Requirement Quantity and Confirmed Quantity, given test case order XXX1, Line Item 2300 and 2301 level.
Provides information about specific fields in program /SAPAPO/SRVF_PROG_CS_STATUS.
In the case of sales order XXX1 item line 2300 and 2301, the substitution product line is 1751529 regardless of the item line number.
This field represents the target product (technical name: TARGET_PROD_ID). Item 2300 and item 2301 have different target products:
Item 2300 represents the sales order data requested by the customer: The customer ordered product 5015485. So the target product of item 2300 is 5015485. Item 2300 does not consider the product which is finally delivered. It is only about the customer requested data.
However ATP found that the customer request should be fulfilled with product 1751529 and ATP created item 2301 for this. So the target product of item 2301 is 1751529.
A sales order consists of different items. The products the items refer to may differ (It may be that a customer orders two different products in one sales order).
There is the possibility that the customer requested item is not displayed in BI.
It is not always possible to determine exactly ONE target product for a sales order: It may be that partly the requested product is delivered to the customer and partly a substitution product. It may even be that several different substitution products are delivered to a customer. So the target product is line dependent. Column "Subst.Prod." may have several different values.