Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

BAPI_SALESORDER_CREATEFROMDAT2 & Confirmed Qty NOT being set

mlychywek
Discoverer
0 Kudos

Good day!

Creating orders via BAPI_SALESORDER_CREATEFROMDAT2. Orders are being created successfully. However, CONFIRMED QTY is set to 0, and NOT triggering.

The following settings have been confirmed.

- Majority of all communication field settings are set to "X" at Header, Item, schedule, and condition.

- All itm_number are set accordingly to respective posnr

- All updateflag are set accordingly

- Set comp_dlv and part_dlv to ' '.

From a functional perspective, what configurations HAVE to be completed to ensure Deliveries are triggered via respective BAPI? I understand, availability check is performed in background so screens cannot be performed--thus, no partial or full delivery can be filled.

Any pointers will be appreciative. Thanks in advance.

6 REPLIES 6

brad_bohn
Active Contributor
0 Kudos

I seem to remember having that issue before. I believe the fix in that particular case was that the storage location was not specified in the BAPI call for items that were ATP-relevant. Of course, if your ATP check is at the shipping point level, if you don't specify the shipping point, you won't get a confirmation either. As usual, I believe I tracked it down with the good old debugger.

0 Kudos

Brad, Thanks for the reply. Shippiing location is mapped correctly.

brad_bohn
Active Contributor
0 Kudos

OK. There shouldn't be a difference in the result, unless there's some other missing parameter in your BAPI call or a user exit is interfering. I would set a breakpoint on function AVAILABILITY_CHECK and compare the calls (and result) from the BAPI and from VA01. That should narrow it down. BAPI_MATERIAL_AVAILABILITY also calls the same function, so you can use that as well.

0 Kudos

Solution: Sales Office field was not populated, but it is NOT a required field either--not having the Sales Office, prevented confirmation from occuring. Simply populate sales office. Not sure if this is a solution for everyone, but it allowed confirmation.

brad_bohn
Active Contributor
0 Kudos

Nice job - that would definitely not be a global solution though since sales office is not really ATP-related. Either you've got a block related to incompletion or some other custom process in play.

0 Kudos

In my case it was the schedule line category that was missing, just in case some one else is stuck here...