For creating a PO we have BAPI’s like BAPI_PO_CREATE1 and BAPI_PO_CREATE, for amending a PO we have BAPI_PO_CHANGE.
For these BAPI’s to work the minimum required data has to be provided.
It is pretty simple to create a normal PO, but little complexity comes in while creating a Simple Services(Services) PO. In this document I would like to deal majorly with creating and amending a services PO, what are the tables that has to be filled, what data that has to be passed to these fileds, where to get this data from and how, so that the BAPI works smooth as honey.
This task has been taken up by me as I see lot of posts on the titled text unanswered or not completely answered.
How to acheive it:
The tables highlighted in the below image are the ones that carry the services information to the BAPI. The information we fill in these tables are crucial (we are taking a scenario where a services PO has to be created from a services PR).
The services line item information should be filled in the POSERVICES table and the accounting information of the service line should be filled in the table POSRVACCESSVALUES.
Filling the POSERVICES table:
Every service line will have a package number assigned to it and every package number has a sub-package number assigned to it.
It is the subpackage number that will have all the service line item information filled in it (like unit price,value,material group etc,) so filling this is very important.
ESLL is the table where all the package realted data is saved for services. It will have service line item related details.
As we are using the scenario where a PO is created from PR,for filling the the table POSERVICES we can use the ESLL entries of the PR. First get the package number of the PR line item(this information is available in EBAN table eban-packno). Pass this package number to ESLL table and get the corresponding sub-package number.
Pass this sub-package number to package number field of ESLL and get all the service line item details like unit price,value,material group etc.
Fill the above obtained data to the POSERVICES table as below.
Every service line item should have two entries in this table, 1 for package number and 2 for subpackage number
poservices–pckg_no = esll–packno. “Package number
poservices–line_no = esll–introw. “Package Line number
poservices–outl_ind = esll–package. “If this is X then it is a service line( because limits also have package numbers, this will act as differentiator)
poservices-subpckg_no = esll–sub_packno. “Sub-Package number
poservices–pckg_no = esll–sub_packno. “Sub-Package number
poservices–line_no = esll–introw. “Sub-Package line number
poservices–quantity = pass quantity(can use esll entry) “PO service quantity
poservices–base_uom = pass UOM(can use esll entry) “Unit of measure
poservices–price_unit = pass Unit Price(can use esll entry) “Unit Price
poservices–gr_price = pass Net Value(can use esll entry) “Net value
poservices–short_text = esll–ktext1. “Short text
poservices–matl_group = esll–matkl. “Material Group
poservices–pln_pckg = esll–sub_packno “Sub-Package number
poservices–pln_line = esll–introw. “Sub-Package line number
The above mentioned are the minimum required fields that has to be passed.
Q: Why poservices–pln_pckg and poservices–pln_line has to be passed ?
A: When a Shopping cart is created in portal a PR will be created in ECC corresponding to it. When a PO is created in ECC refering to this PR, in the Shopping cart also this PO number should be update in the related documents tab.
Only when you pass the above two fields this will happen.
Filling the POSRVACCESSVALUES table:
As mentioned above this table will have the acounting information of the service line. This table will have only one entry corresponding to the service line.
The accounting information of a service line is stored in the table ESKL with reference to sub-package number of the above service line item.
So take the above sub-package number, pass it to the package number field of the ESKL table and get the accounting details.
Fill the above obtained data to the POSRVACCESSVALUES table as below.
posrvaccessvalues–pckg_no = eskl–packno. “Sub-Package number of ESLL entry
posrvaccessvalues–line_no = eskl–introw. “Line number of eskl
posrvaccessvalues–serno_line = eskl–numkn. “Seq. Number of Acc. Assignment Specification: Service Line
posrvaccessvalues–serial_no = eskl–zekkn. “Sequential Number of Account Assignment in ESKN
posrvaccessvalues–quantity = pass quantity(can use eskl entry) “PO service quantity
This way both the services tables should be filled and passed to BAPI.
*Note: Along with these tables all the required tables as shown in the above screen shot are also to be filled for the BAPI to work. Here we only covered service realted data.