Hello Shohei,
"OLTP Object Type(*)" is of more importance to the external system; surely, it would be assigned after the number is changed by the CIF .
The document is created an send it to R/3 or ECC (if you have publication types, Integration models, etc...); when the external system confirm the document and return it to SCM via CIF, the "OLTP Object Type(*)" should be assigned.
Probably you only have this number for documents working on planning version 000, and not for other planning versions.
At the end: "OLTP Object Type(*)" is decided by the external system, when documents go trough CIF.
Please check the following documentation:
"Order Category in OLTP System
The (OLTP or R/3) order category is used in addition to the order number to identify an order that has been transferred from an external (or R/3) system to the APO system.
Some examples of order categories are sales orders (fixed value 3), purchase orders (fixed value 2), and production orders (fixed value 6).
You can use various (OLTP or R/3) order categories for certain APO business objects, such as production orders or in-house production.
For example, a procurement order (BUS10502) in the APO system can contain both procurement orders (category 2) and purchase requisitions (category 1). In APO, the order category is only used to identify an order in combination with the order number. The category is also used in part to determine if an order/schedule line in the APO system can be changed by a user or not (a purchase order, for example, may no longer be changed, while a purchase requisition may still be changed). Generally, the order category is of more importance to the external system. For example, the R/3 system needs to know whether it is a purchase order or a purchase requisition that is being dealt with.
If an SAP (e.g. R/3) system is not linked to the APO system, and this system is to be used to exchange the order information that requires a certain order category, we recommend that you use the standard values, for example category 2 for business object BUS10502.
Orders that are created within an APO system, for example in a planning run, are not given an (OLTP) order category when created, since they were not transferred to the APO system from an external system. These orders all automatically receive (for example, when they are imported) the order category 8 (APO local order). These orders have an APO internal order category which distinguishes between criteria such as in-house production or external procurement. In a subsequent (optional) step, an external system can then decide whether an order created in APO is a purchase order (category 2) or a purchase requisition (category 1) and assign it an (OLTP) order category and an (external) order number.
You find these values in the documentation of the respective function or of the domain fixed values.
Note that certain functions (for example, configurations) are only possible for certain order categories."
Regards,
Gustavo Pérez
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.