Performance increase of BAPI

[Former Member]

Hi,

We have developed a new navigation platform for creation of purchase order with purchase requisition. Here we are selecting "n" number of PR and selecting proper parameters, converting it to PO for a specific vendor. For this purpose we are using a standard BAPI for PO creation. This is taking too much of time. For converting 200 PRs into 1 PO, system is taking 90 min (minimum). We want to increase this performance to 4sec.

Request you to please suggest some enhancement

Regards

Amit Parkhi

[Former Member]

Directly fetch data of PR from table and end that data to Bapi PO create in one stroke...

like header and item data....

[Former Member]

Hi,

thanks for suggestion. But this cannot be performed as there are other selection criteria for creation of PO like purchase organization, vendor, number of PR, materials. The BAPI runs for each material and hence it takes time. This process needs to be performed at faster rate.

Regards

Amit Parkhi

[Former Member]

when you are creating only one PO then whay it isnot possible....

because for all itms header data is same....

and if item data is different then you can put it in item data...

ya but if u r taking item data from user then... i think there is no option.... it will take time to tak input....

but if this data is same for all items then you can send it in one stoke...

Moderator message: please do not use SMS speak.

Edited by: Thomas Zloch on Nov 2, 2010 6:01 PM

[Clemenss]

Hi Amit,

- do not COMMIT WORK after every single BAPI call. Depending on how many locks are set, you may wait for 20, 50, 100 or alle PO's BAPI calls.

- if this is still not sufficient, you may consider parallel processing. You may split the total number into different batches (files?) and start them at the same time (4-6 batches). Or you create a capsule for the BAPI and call this in parallel.

Regards,

Clemens

[brad_bohn]

I would also suggest that you trace the different parts of the process as well. Is the time lag in the BAPI call itself or in the external processing? Have you checked for performance related notes? Are you sure that the time lag is application processing or update processing or is it user exit related? If you are in fact, merging 200 PR's into 1 PO, I doubt 4 secs is a realistic goal, but 90 minutes is definitely not acceptable either. If you don't have any Z-processing interference, raise the issue with SAP via OSS.