Question Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2 in Enterprise Resource Planning Q&A

BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Fri, 09 May 2014 05:45:55 GMT

Greetings,

Just doing some development and I am aware of how to create quotations and orders as well but this time, it seems that I keep running into a strange error, error from which I cannot go forward.

I do call the right parameters and the order is saved but it is rolled back after the creation of the SD order.

The error that I'm still getting is this:

[3] => Array

(

[TYPE] => W

[ID] => V1

[NUMBER] => 555

[MESSAGE] => The sales document is not yet complete: Edit data

[LOG_NO] =>

[LOG_MSG_NO] => 0

[MESSAGE_V1] => VBAPKOM

[MESSAGE_V2] => 000010

[MESSAGE_V3] =>

[MESSAGE_V4] =>

[PARAMETER] => VBUVKOM

[ROW] => 0

[FIELD] =>

[SYSTEM] => DEVCLNT200

)

You can see my request and my response in the attached screenshots.

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

jpfriends79 — Fri, 09 May 2014 06:24:36 GMT

There are 2 thinsg to this:

1. Hope you are using Function Module(FM) - BAPI_TRANSACTION_COMMIT along with FM - BAPI_SALESORDER_CREATEFROMDAT2 in test sequence.

2. Generally, message V1 555 - The sales document is not yet complete: Edit data is associated with incompletion log. It would be better, if you check your Incompletion log config and compare with your parameters provided in FM. Thus, I would suggest, simply create desired sales doc manually with parameters you are providing as input in FM.

In addition to that, make sure you are passing all the mandatory parameters in FM. Just pointing this out based on screenshot provided by you, like

- mandatory Pricing condition type,

- mandatory Partners in item (AG. WE, RE, RG)

- Requested Delivery Data

Thanks, JP

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

Lakshmipathi — Fri, 09 May 2014 06:39:41 GMT

Carry out the code corrections as recommended in the following note:-

Note 603131 - BAPI SD: Incorrect incompleteness messages

G. Lakshmipathi

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

PhanikumarV — Fri, 09 May 2014 06:58:22 GMT

Also in standard QT preparation--system will ask for Validity period.(valid to for this QT)

(VBAPKOM--10 the incompletion procedure assigned for Standard QT )

ensure this should be in your Input parameter for your FM.

Phanikumar

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

madhu_vadlamani — Fri, 09 May 2014 07:01:46 GMT

Hi,

Do you have variant configuration.

Regards,

Madhu.

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Fri, 09 May 2014 08:45:23 GMT

Thanks, but it is the same problem and I cannot figure it out.

Based on the SAP NOTE it is an ABAP issue, and I write in PHP.

Also, I did want to create the order from the GUI, but I do get the same error -> see attached screenshot

It does not say what kind of error it is or for what field ...

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

jpfriends79 — Fri, 09 May 2014 09:41:30 GMT

On GUI, instead of using FM to create. Use TCode VA01. with this system will indicate you the relevant fields for which you are getting incompletion log(Error Message V1 555)

Thanks, JP

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Fri, 09 May 2014 11:57:58 GMT

The order is created without problems in VA01 ... so annoying

If i create it with a refference to a Qutation, without items, it gives no error, the returned salesorder number is okay.

But then, SD document 1063335 is not in the database or has been archived.

In the WEB i do call COMMIT ... and no errors, but the document cannot be accessed.

Array

(

[1] => Array

(

[TYPE] => S

[ID] => V4

[NUMBER] => 233

[MESSAGE] => SALES_HEADER_IN a fost prelucrat cu succes

[LOG_NO] =>

[LOG_MSG_NO] => 0

[MESSAGE_V1] => VBAKKOM

[MESSAGE_V2] =>

[MESSAGE_V3] =>

[MESSAGE_V4] =>

[PARAMETER] => SALES_HEADER_IN

[ROW] => 0

[FIELD] =>

[SYSTEM] => xxxx

)

[2] => Array

(

[TYPE] => S

[ID] => V4

[NUMBER] => 233

[MESSAGE] => SALES_ITEM_IN a fost prelucrat cu succes

[LOG_NO] =>

[LOG_MSG_NO] => 0

[MESSAGE_V1] => VBAPKOM

[MESSAGE_V2] => 000010

[MESSAGE_V3] =>

[MESSAGE_V4] =>

[PARAMETER] => SALES_ITEM_IN

[ROW] => 1

[FIELD] =>

[SYSTEM] => xxxx

)

[3] => Array

(

[TYPE] => S

[ID] => V1

[NUMBER] => 311

[MESSAGE] => Vanzare 2667587 salvat

[LOG_NO] =>

[LOG_MSG_NO] => 0

[MESSAGE_V1] => Vanzare

[MESSAGE_V2] => 2667587

[MESSAGE_V3] =>

[MESSAGE_V4] =>

[PARAMETER] => SALES_HEADER_IN

[ROW] => 0

[FIELD] =>

[SYSTEM] => =xxxx

)

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

jpfriends79 — Fri, 09 May 2014 12:46:26 GMT

Then better debug the transaction SE37 for the FM BAPI_SALESORDER_CREATEFROMDAT2, where focus on the data getting processed under:

Program SAPMV45A
Include MV45AF0B_BELEG_BEARBEITEN_ENDE
Structure VBUVVB

For

 [MESSAGE] => Vanzare 2667587 salvat

Use TCode VA23 to view quotation 2667587

Thanks, JP

Re: BAPI Problem -> BAPI_SALESORDER_CREATEFROMDAT2

Former Member — Mon, 12 May 2014 13:23:51 GMT

Got it solved, I did call in the Header INX two lines.

$ORDER_HEADER_INX['UPDATEFLAG'] = 'I';

$ORDER_HEADER_INX['PURCH_NO_C'] = (string) $oferta;

Took out these two lines and everything started to work without problems.