topic Re: BAPI_GOODSMVT_CREATE for MB01 in Application Development and Automation Discussions

BAPI_GOODSMVT_CREATE for MB01

former_member182371 — Wed, 09 Mar 2005 14:13:35 GMT

Hi,

i´m using

BAPI_GOODSMVT_CREATE

for MB01
.
The message i´m getting is as follows:
message type = 'E'
message ID = 'LB'
message num. = '031'
message text = 'of the required quantity of material

013F1RE1101PB000, 3,000 HOJ remain(s) open
'.
What does this message mean?.

Best regards

Re: BAPI_GOODSMVT_CREATE for MB01

Former Member — Wed, 09 Mar 2005 15:34:02 GMT

Lack of info...

Perhaps you should check oss note #526850 (or 734850)

It describes some occurence of this error message and circumstances in which it occure.

HTH

Ivaylo

Re: BAPI_GOODSMVT_CREATE for MB01

Former Member — Wed, 09 Mar 2005 15:54:14 GMT

Try performing the MB01 transaction online for the same data and see if you get the same message. If you are getting the same message then that means you should look at the OSS notes mentioned above for clues in config and/or code. But if you are getting it only in your BAPI call, then something that you are passing in the BAPI is triggering it. But still reading the notes above will give you a clue.

Srinivas

Re: BAPI_GOODSMVT_CREATE for MB01

former_member182371 — Wed, 09 Mar 2005 17:00:55 GMT

Hi,

Now my doubt is the following:

when using BAPI_GOODSMVT_CREATE for MB01

<b>should i pass two registers</b>: one for Movement type 101 and another one for 543?

<b>or just one</b> for 101 and then 543 is done automatically?

Best regards

Re: BAPI_GOODSMVT_CREATE for MB01

Former Member — Wed, 09 Mar 2005 18:46:55 GMT

Hi,

Looks like you are trying to do both Goods Receipt(101) and a goods issue for a sales order(543) in the same function call. Can you explain what is the program trying to achieve?

Are your unit of receiving same as the unit of issue? If they are different, then there may be some residual quantities leftout due to unit conversions.

Srinivas

Re: BAPI_GOODSMVT_CREATE for MB01

former_member182371 — Thu, 10 Mar 2005 08:18:58 GMT

Hi,

what i´m trying to do with the bapi is to

replicate transaction MB01

.
When i try to do it by means of transaction MB01 my input data in the 1st screen is:
movement type = 101
purchase order / item
Plant
Storage Location
In the 2nd screen i click on "+Adopt + details+" pushbutton.
In the 3rd screen i click enter and i get the message:

Caution! Internal number allocation for materials handled in batches.

I accept an then warning message "14 characteristic attributes have been adopted from original batch center/material/po" appears.

i click intro and then i introduce the batch in question.

In this screen is where

movement type 543

appears and this is the reason of my former question.

Best regards.

Re: BAPI_GOODSMVT_CREATE for MB01

former_member182371 — Thu, 10 Mar 2005 12:21:28 GMT

Please,

does anyone of you know how to do as MB01 but with a bapi?

Any example or hint will be greatly appreciated.

Best regards.

Re: BAPI_GOODSMVT_CREATE for MB01

Former Member — Thu, 10 Mar 2005 16:09:00 GMT

Try setting the 'Delivery completed indicator', if that is applicable in this situation. I think the system thinks that there is some residual amount left to be received and may be your config requires it to be received in total before issuing it.

Did you check if the unit of issue(in sales view, sales unit) and the unit of receipt(in purchasing view) are the same for this material?

Also, some of these messages are configurable, in the sense that a configuration person can set this message to be a warning or information message, instead of an error message. System will issue the message accordingly, instead of the error message that you are getting now.

Regards,

Srinivas

Re: BAPI_GOODSMVT_CREATE for MB01

Former Member — Fri, 11 Mar 2005 00:03:35 GMT

We are using the same BAPI for GoodsMovement but not for the movement types that you mentioned. WE use it though for different movm't types, and one after the other.

Though it seems the BAPI allows multiple movement type based on the GOODSMVT_ITEM table parameter, in our case, we still made a separate call for different movement types.

Hope that helps.