Start of Content Area

Background documentation Resending Objects  Locate the document in its SAP Library structure

You trigger the resending of objects for which postprocessing records were generated in CIF error handling by choosing Send to APO This graphic is explained in the accompanying text APO or Send to R/3 This graphic is explained in the accompanying text R/3.

The system usually transfers the current object status, which means it takes into account whether an object has been changed since the last transfer. This prevents an object being overwritten by an “obsolete” status.

The transfer sequence within a qRFC LUW plays a significant role in the transfer from SAP R/3 to SAP APO, but not in the opposite direction. As a result, the system behavior when objects are resent differs depending on the transfer direction.

Note

If you are working with production campaigns, you first have to transfer the planned and manufacturing orders, then the campaigns.

...

Resending from SAP R/3 to SAP APO

If errors occur during the transfer from SAP R/3 to SAP APO, CIF error handling ensures that serialization is avoided. If errors continue to occur in the target system when the data is resent from SAP R/3 to SAP APO, serialization is again avoided. When resending objects, the sequence of RFCs (that is, the block formation) must be the same as in the qRFC LUW of the original transfer. This requirement leads to the following system behavior:

·        You send an object for which a postprocessing record already exists to SAP APO, but not from CIF postprocessing.

¡        If the transfer proceeds without errors, the object is posted to the target system. The postprocessing record that already exists continues to exist and its processing status does not change.

¡        If an error occurs in the transfer, a new postprocessing record is generated. The postprocessing record that already exists continues to exist and its processing status does not change.

·        You resend an object for which a postprocessing record already exists to SAP APO from CIF postprocessing.

¡        If the transfer proceeds without errors, the object is posted in the target system and the existing postprocessing record receives the status Processed.

¡        If an error occurs again during the transfer, a new postprocessing record is generated. The postprocessing record that already exists receives the status Processed.

Note

Prerequisite postprocessing records are also automatically transferred.

Resending from SAP APO to SAP R/3

In this case, block formation can occur arbitrarily. This leads to the following system behavior:

·        You send an object for which a postprocessing record already exists to SAP R/3, but not from CIF postprocessing.

¡        If the transfer proceeds without errors, the object is posted in the target system and the existing postprocessing record receives the status Obsolete (automatically set by system).

¡        If an error occurs in the transfer, a new postprocessing record is generated. The postprocessing record that already exists receives the status Obsolete (automatically set by system).

·        You resend an object for which a postprocessing record already exists to SAP R/3 from CIF postprocessing.

¡        If the transfer proceeds without errors, the object is posted in the target system and the existing postprocessing record receives the status Processed.

¡        If an error occurs in the transfer, a new postprocessing record is generated. The postprocessing record that already exists receives the status Processed.

 

 

End of Content Area