topic Re: BAPI for SALES ORDER in Application Development and Automation Discussions

BAPI for SALES ORDER

Former Member — Thu, 26 Jun 2008 05:45:15 GMT

Hi Experts,

1 ) Sample code for Sales order chage , sales order Delete

please ?

2) I want to test BAPI_SALESORDER_CHANGE in se37...what is schedule line in that case.

or step to test it in se37 only.

<removed by moderator>

Edited by: Mike Pokraka on Aug 4, 2008 2:45 PM

Re: BAPI for SALES ORDER

Former Member — Thu, 26 Jun 2008 06:00:58 GMT

Hi,

see

https://forums.sdn.sap.com/click.jspa?searchID=13348419&messageID=4734026

Regards

Kiran Sure

Re: BAPI for SALES ORDER

Former Member — Thu, 26 Jun 2008 06:03:52 GMT

Monica,

just refer:

Amit.

Re: BAPI for SALES ORDER

Former Member — Thu, 26 Jun 2008 06:06:03 GMT

<removed_by_moderator>

Edited by: Julius Bussche on Aug 26, 2008 11:46 AM

Re: BAPI for SALES ORDER

GauthamV — Thu, 26 Jun 2008 06:09:45 GMT

hi,

see this documentation,it will help u test from se37.

BAPI_SALESORDER_CHANGE

Text

Sales order: Change Sales Order

Functionality

You can use this method to change or delete sales orders.

You can change header, item, schedule line and configuration data.

In general, note that you should:

Only specify fields that should be changed

Select these fields by entering an X in the checkboxes

Enter a U in the UPDATEFLAG field

Always specify key fields when changing the data, including in the checkboxes

The configuration is an exception here. If this needs to be changed, you need to complete it again fully.

Maintain quantities and dates in the schedule line data

Possible UPDATEFLAGS:

U = change

D = delete

I = add

Example

1. Delete the whole order

2. Delete order items

3. Change the order

4. Change the configuration

Notes

1. Minimum entry:

You must enter the order number in the SALESDOCUMENT structure.

You must always enter key fields for changes.

You must always specify the update indicator in the ORDER_HEADER_INX.

2. Commit control:

The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

Parameters

SALESDOCUMENT

ORDER_HEADER_IN

ORDER_HEADER_INX

SIMULATION

BEHAVE_WHEN_ERROR

INT_NUMBER_ASSIGNMENT

LOGIC_SWITCH

NO_STATUS_BUF_INIT

RETURN

ORDER_ITEM_IN

ORDER_ITEM_INX

PARTNERS

PARTNERCHANGES

PARTNERADDRESSES

ORDER_CFGS_REF

ORDER_CFGS_INST

ORDER_CFGS_PART_OF

ORDER_CFGS_VALUE

ORDER_CFGS_BLOB

ORDER_CFGS_VK

ORDER_CFGS_REFINST

SCHEDULE_LINES

SCHEDULE_LINESX

ORDER_TEXT

ORDER_KEYS

CONDITIONS_IN

CONDITIONS_INX

EXTENSIONIN

Re: BAPI for SALES ORDER

Former Member — Fri, 18 Jul 2008 08:29:57 GMT

Thanks to all,

Amit & kiran.