Functionality The Check purchase order> method checks whether the data from apurchase order> that is relevant forAccounting can be posted. Running this method does not generate adocument or number assignment in Accounting. If a purchase order is created for material in Logistics, the expectedcosts are transferred to Accounting as purchaseorder commitments>. Depending on the Customizing settings made forcommitments, the following commitments recipients are possible:
- Controlling object (such as cost center, internal order, and project)
- Cash management and forecast>
- Cash budget management>
- Funds Management>
- Cash management project
Notes In most cases, first use the Check purchase order> method, andthen run the method Post purchaseorder>. INCLUDE BAPI_RETFurther information For more details, refer to the following documentation in the R/3Library:
- Cross-Application Components> -> Business Framework
Architecture> -> Business Application Programming>: BAPI User Guide> BAPI Programming>
- Cross-Application Components> -> General Application
Functions> -> Interfaces to Accounting>: BAPIs for Transferring Data to Accounting> trados = fiDescription This parameter is optional and determines the following: Whether ERP-internal application categories (parameter obj_type), suchas PREQ for an ERP purchase requisition, can also be used in theinterface. If the ERP commitment commutation logic can be used for CO commitmentsmanagement and cash budget management. The parameter can only be used internally by SAP. It is not maintainedfor use in customer programs or modifications (see SAP Note 83020). Value range The parameter can be initial or have the value 'X'. Default The parameter is not set. INCLUDE ACC_BAPI_PURCHASEAMOUNT OBJECT DOKU ID TX INCLUDE ACC_BAPI_PURCHASEORDER OBJECT DOKU ID TX INCLUDE ACC_BAPI_PURCHASEREQUI OBJECT DOKU ID TX INCLUDE ACC_BAPI_RETURN OBJECT DOKU ID TX
|