In the post POS DM era, a hurdle appears in SAP CAR: When WPUUMS data is sent from CAR to downstream systems, different IDoc numbers make it difficult to reconstruct the links to the original document. But there is a remedy.
It's not easy to keep track of all the data, especially in retail. In our experience, the criteria defined for aggregating data in an IDoc can differ from customer to customer, e.g., by day, store, etc. The system summarizes and aggregates IDocs and generates billing and FI documents. So far, so good.
As long as you use POSDM, the link to the original receipt or single document is usually still given. However, this is not the case with more recent releases of SAP CAR. When sending data to subsequent systems, e.g. SAP Retail, the IDoc (identical in content) receives a new number. As a consequence, a link criterion seems to be missing to update the document flow in a comprehensible way.
However, SAP provides a solution: the package ID. When IDocs are sent from SAP CAR to subsequent systems, this package ID is also sent without being changed. This is where we come in to ensure that the document flow also remains traceable retrogradely - from the billing and financial accounting document to the individual receipt.
Why is this important for us? With our SAP AddOn Receipt4S® we enable our retail customers to manage their POS data in a way that KassenSichV-conformity and to ensure convenient Z1, Z2 and Z3 access in the event of an audit. The legislator also stipulates that the path from the individual receipt to the invoice/FI document and vice versa must be traceable. For this reason, we are constantly keeping ourselves up to date in order to ensure compliance with the guidelines for you in the future as well.
You can find more information about Receipt4S® at www.receipt4s.de.
