BAPIPOCREATE1 다양한 Condition을 사용한 사례 BAPI / SAP 모듈별. Customizing 되었다면 PB00을 BAPI를 이용하여 수정 할 수 없게 된다. Bapi Po Create1 Manual Price 10/4/2019 Create an Employee using PA30 By Arpita Karmakar, ABAP & XI Fast Trac Manager, IBM India Go to PA30.Enter a new Employee Number.

Symptom

Bapi Po Create1 Manual Price In India

When creating a purchase order by BAPI_PO_CREATE1, net price is not taken from input data in POITEM-NET_PRICE.

Environment

SAP ERP
SAP enhancement package for SAP ERP
SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA ; SAP enhancement package for SAP ERP all versions

Keywords

ECC, BAPI, BAPI_PO_CHANGE, BAPI_PO_CREATE1, PRICE, CONDITION, PB00, PBXX, PO_PRICE, POITEM-PO_PRICE, PBUEB, NO_PRICE_FROM_PO, POCOND, POCONDX, POCONDHEADER, POCONDHEADERX, POCOND-CHANGE_ID, CHANGE_ID, CONDITION CATEGORY, GROSS, NET PRICE, INFORMATION RECORD, CONTRACT, ME21N, ME22N, ME31K, ME32K, ME33K, INFOREC, INFORECORD , KBA , MM-PUR-PO-BAPI , BAPIs - Purchase order , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.

Skip to end of metadataGo to start of metadata Bapi Po Create1 Manual Price

Purpose

The aim of this page is to explain the functionality of the Purchase Order creation through BAPI_PO_CREATE1 function module.

Overview

BAPI_PO_CREATE1 is a Business Application Programming Interface which enables you to create Purchase Orders from external systems or specific internal processes. The BAPI provides the same functionalities as the online transaction ME21N. Alternatively, the IDoc type PORDCR1 is available. This IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1. You can run the BAPI by entering the t-code SE37 in ECC and executing the function module BAPI_PO_CREATE1.

The Structure of BAPI_PO_CREATE1

Through the BAPI Explorer transaction (t-code BAPI) you can reach the structure of BAPI_PO_CREATE1 in any ECC system. In BAPI, select the path Materials Management > Purchasing > PurchaseOrder > CreateFromData1. A detailed description of the BAPI-structures as well as example of how to fill the BAPI are available under the Documentation tab.

PO Header

All information usually given in the Purchase Order header are supplied in the structure POHEADER. Some example with the BAPI-field name: Document type DOC_TYPE, Vendor VENDOR, Payment Terms PMNTTRMS, PO Currency CURRENCY, Company code COMP_CODE, Purchasing Organization PURCH_ORG and so on. To decide which header fields are necessary for you, you could set the POHEADERX structure respectively. If no POHEADERX fields are selected, no header fields will be mapped through the BAPI.

Technical fields

If ticked, TESTRUN flag means your BAPI-process will run with no database effect. Opposite to this, in case you want to write your data into database, the best way is to create Test sequences:
1. Go to the first screen in SE37 and choose the menu Function Module > Execute > Test Sequences.
2. In the upcoming list, in order, give the Function BAPI_PO_CREATE1 and BAPI_TRANSACTION_COMMIT. Press button Execute.
3. Both BAPIs will be executed in sequence. For BAPI_PO_CREATE1 select the test data you saved in Test Data Directory. For BAPI_TRANSACTION_COMMIT just press Execute.

MEMORY_COMPLETE and MEMORY_UNCOMPLETE are responsible for setting the PO into 'Held' status.

NO_MESSAGING indicator is responsible for triggering output for a Purchase Order - in case it is set to 'X', no output will be determined. By default NO_MESSAGING indicator is set for SRM Purchase Orders in extended classic scenario. In addition to that the message PurchaseOrderERPRequest_Out_V1 is also not triggered for such PO.

The import parameter 'NO_AUTHORITY' allows to skip authorization check when executing the BAPI. Also when you call the BAPIs, the authorization is now no longer checked for the transaction code. The authorization objects for the respective documents such as M_BEST_EKO, M_BEST_EKG and M_BEST_BSA are, however, continually checked.

PO Item

The main BAPI-structure of your Purchase Order item data is the POITEM and the POITEMX. Usual item data such as material (MATERIAL), plant (PLANT), item quantity (QUANTITY), Item price (NET_PRICE) are given here.

The field item category (ITEM_CAT ) plays the same role as the respective field in ME21N's Item overview. You can also give here the Account Assignment category (ACCTASSCAT) which will be then completed with the Accounting data of the structure POACCOUNT and POACCOUNTX.

Calculation type field (POITEM-CALCTYPE) is responsible for triggering new pricing for a PO item
* pricing type 'A' which means that the pricing condition will not be determined again.
* pricing type 'B' means that the pricing will be redetermined.
* pricing type 'C' means that the manual pricing elements will be copied and others redetermined.
In any cases, the field POITEMX-CALCTYPE should be sent as 'X'.

•PO_PRICE = ' ': The price determination is carried out as before.
•PO_PRICE = '1': The value assigned in field NET_PRICE is transferred as a gross price, that is it is set in the condition type that is defined as a base price in the calculation schema. All other condition types remain unchanged. No conditions are copied from the last document.
•PO_PRICE = '2': The value assigned in field NET_PRICE is transferred as a net price, that is it is set in the condition type that is defined as base price in the calculation scheme. All other condition types are deleted.

Missing Functions

There are restrictions because of technical reasons. These limitations of the BAPI are enumerated under the SAP Note 197958 - BAPIs for purchase orders: Missing functions.

Working with Test data in BAPI_PO_CREATE1

In case you have a prepared Test data you can simply run it by clicking the 'Execute' button or pressing F8. To enable debugging a specific Test data, you should click 'Debugging' or hit Ctrl + F7 what will run the BAPI in debugger mode. 'Test data directory' push button enables you to track back already prepared Test data and you can create/save/delete your current data to that same test directory.

Examples of BAPI Test data

Examples about how to fill a BAPI with a given set of ready-made data are available in the following SAP Knowledge Base Articles [no ABAP-code inside]:

KBA 2134946- Sample of BAPI_PO_CREATE1 Test Data for Material PO Transferred from SRM
KBA 2134968- Sample of BAPI_PO_CREATE1 Test Data for Service/Limit PO

Custom Codes in BAPI

By populating the parameter EXTENSIONIN of the BAPI, you could transfer your own fields for header, item, or account assignment data. The structures which holds the custom fields should contain the same fields in the same sequence. That is, for purchase order CI_EKKODBX should contain the same fields in the same sequence as defined in CI_EKKODB and CI_EKPODBX should contain the same fields in the same sequence as defined in CI_EKPODB.

On the other hand, there are customer exits (function modules) available for the BAPI BAPI_PO_CREATE1:
•EXIT_SAPL2012_001 (at start of BAPI)
•EXIT_SAPL2012_003 (at end of BAPI)

and for BAPI_PO_CHANGE:
•EXIT_SAPL2012_002 (at start of BAPI)
•EXIT_SAPL2012_004 (at end of BAPI)