The BAPI_INTERNALORDER_SAVEREPLICA function module is only usedinternally for internal orders (in SAP ALE business processes). To create a new internal order, you therefore need to use theBAPI_INTERNALORDER_CREATE function module. This executes a complete check on the order before you save.
You can replicate an internal order (order category 01 and 02) usingthe BAPI_INTERNALORDER_SAVEREPLICA in an ALE business process within an external R/3 system (so called receiver system).
Furthermore, the system sets the corresponding status for the order in the same receiver system.
The "Availability control active" and "Budget tolerances exceeded"statuses are always set to inactive in the receiver system. This isregardless of the status in the order master system. The reason forthis, is that an order can only have a budget in its own master system,
meaning that an availability control is not possible in the receiver system.
The system checks whether the organization units entered in the order(such as company code, controlling area and so on) are valid for the current date.
Further checks are not carried out in the receiver system. This means
that no authorization checks or status checks of any kind are carried out.
An order already in the receiver system is only overwritten if its master system corresponds to the logical system in theMASTERDATA-LOGSYSTEM field.
If the order was assigned to a WBS element that does not exist in the
order receiver system, then the assignment is disregarded during replica assignment. The "Assigned WBS element" field in the ordermaster stays blank.
If the "Deletion indicator can be archived" status is contained in theOBJECTSTATUS import table, and is marked as active, the corresponding
order in the receiver system is deleted, including all its dependent tables.
For further information, see documentation in ALE business processes for internal orders.