topic BAPI_MATERIAL_AVAILABILITY in Application Development and Automation Discussions

BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 08:03:50 GMT

Has anyone used this function ??

It does what we need, but it takes a lot of time.

We have to process about 2500 sales ordes with about 25.000 lines, and it takes hours to process them. Without this function the hole process takes about 12 minutes.

What other solution do we have, or what is the problem with this function ????

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 08:25:19 GMT

Hi Ivanov,

You can also run, BAPI_SALESORDER_SIMULATE which if you pass sales order line items, will return the proposed delivery date for them (having performed an availability check). The benefit of this is you are not restricted to one item per call, so you don't get the overhead for each item.

I have used BAPI_MATERIAL_AVAILABILITY quite a bit and haven't noticed it to be prohibitively slow. There are, however, lots of customising settings fot ATP that could impact your performance (scope of check, use of APO, etc.). Also, be aware that when you perform availability checks you are setting up lock entries for material plant combinations, which can cause subsequent calls to be queued. You should design your threads carefully.

How are you processing the sales orders that you can process 25000 lines in 12 minutes? Are you saving them into SAP?

Hope this helps. Perhaps you could post a little more on what you are doing.

Cheers,

Brad

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 08:39:22 GMT

I am using the function sales_document_create.

Maybe will be 20 minutes after all, depends on the hour, but we will process them at night.

You probably have right Brad, with the lock mecanism, because this is what i've noticed.

For the first 200, 300, orders, the time is not exeptionaly but resonable, after that..... more and more time. hours....

I could use the "simulate solution", at least try it.

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 08:50:29 GMT

If you save them into SAP, why do you perform an availability check first?

Can't you just get the results from when you create the sales orders? Or does the result of the ATP check affect what you put into the order?

If locking problems are what you are encountering, you will get them also with SIMULATE, but at least you can process bundles rather than one material at a time.

Just for my understanding do you sequnce the calls like this:

1. Availability check

2. Post order

1. Availability check

2. Post order ...

or do you do all the availability checks first and then post the orders?

Cheers,

Brad

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 09:03:30 GMT

I can not do the availability check when I save the order because :

the invoice is made in another system, with an exact quantity and value. i have to introduce into sap the same invoice. So, if I have o position with 2 on quantity and in stock i have 1, the order is saved with 1, and this is not good for me. so , i have to make the check before i save the order.

the check is made, as you said, in this sequence

1. Availability check - line by line, this means, material by material,

2. Post order

1. Availability check- line by line,

2. Post order ... etc...

Mabe the sequence is wrong ?

Or is it better to call the BAPI_MATERIAL_AVAILABILITY after the order is saved, but not commited, in this case I can put into the parameters of the function the document number also ???

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 10:00:42 GMT

Hi Ivanov,

It sounds like you are running an FI only solution, yes?

Do you care about ATP checking at all? Maybe you could switch it off in the sales order/delivery?

Another idea (assuming you need ATP), borrowing off your commit concept, is to do the following:

1. Create the order (without commit)

2. Check the availability results of each line in the order to ensure full quantities

3. If all lines ok, COMMIT

4. If some lines not ok, use the results to calculate dates when all lines will be ok

5. ROLLBACK the order

6. Post a new order with new line item dates

7 COMMIT

This will help a lot, as (depending upon your industry) generally items are available for orders, and only on an exception basis will you be required to do additional processing (and you will avoid doing additional ATP calls).

Cheers,

Brad

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 10:22:19 GMT

Yes, it's a good idea, but...

the sale order does not save without a commit.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

So, how can I return with rollback ??

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 10:29:38 GMT

Taking my steps (more technical view):

1. You can call the BAPI to create the order

2. Check the parameters returned by the BAPI (for availability results)

3. If all lines ok, call function 'BAPI_TRANSACTION_COMMIT' and finish

4. If some lines not ok, then determine dates when all lines will be ok

5. Call function 'BAPI_TRANSACTION_ROLLBACK'

6. Call BAPI again to create the order

7 Return to step 3.

Does that make sense?

Brad

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 10:34:31 GMT

One downside to this approach is that each time you ROLLBACK a sales order you will lose that order number. This will lead to occasional gaps in your order numbers. This may or may not be an issue for you.

Brad

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 11:56:19 GMT

" 2. Check the parameters returned by the BAPI (for availability results) ".

Here is the problem... What is the parameter that tells me that req. quantity = confirmed quantity ??

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 13:17:12 GMT

Hi Ivannov,

Sorry, i mixed up BAPI_SALESORDER_SIMULATE with BAPI_SALESORDER_CREATEFROMDAT2.

There is no return parameter from BAPI_SALESORDER_CREATEFROMDAT2 to check the schedule lines, but you have a few options:

- in the USEREXIT_SAVE_DOCUMENT export the XVBEP internal table to memory. You can then import it into your calling program and use it for your processing

- If you are calling the BAPI from outside of SAP you could interpret the XVBEP table in USEREXIT_SAVE_DOCUMENT and issue messages (MESSAGE I100 with ...) that should be returned to you in the RETURN parameter of the BAPI (haven't tested this, but should work).

Also, with regards to the gaps in the number ranges that I mentioned in a previous post, you can overcome this by using an external number range on your sales order (and use the NUMBER_GET_NEXT function to generate your own) only generate a new one for each actual new sales order. Thus, when you do rollback work, you just keep that number and re-use it for the next call of the create order bapi.

This might sound a bit elaborate, but the performance improvement (given your initial figures) will be enormous.

Brad

Message was edited by: Brad Williams

Re: BAPI_MATERIAL_AVAILABILITY

Former Member — Fri, 20 May 2005 14:47:21 GMT

Hi Ivanov,

How is it progressing?

Do you think that this process can work for you?

Cheers,

Brad