Problem in updating the partners data for sales order

hi all..
am using bapi_salesorder_createfromdat2 to create salesorder..
in the bapi am passing the partners data as follows..
partner-partn_role = 'ZD'.
partner-partn_numb = <cust.no.>
partner-itm_number = <item no.>
after that..,the sales order is created succesfully .but now the problem is the partner data as shown above is not updated successfully in the item level details of sales order..
is there any way to fix it ?
please help me with the possible alternatives.
thanks in advance
suresh

Hi Suresh,
*Fill partner
wa_order_partnr-partn_role = 'AH'.
wa_order_partnr-partn_numb = '0000100001'.
"wa_order_partnr-itm_number = '000010'.
INSERT wa_order_partnr INTO TABLE tab_order_partnr.
wa_order_partnr-partn_role = 'WE'.
wa_order_partnr-partn_numb = '0000100001'.
"wa_order_partnr-itm_number = '000010'.
INSERT wa_order_partnr INTO TABLE tab_order_partnr.
Is it a standard partner function or custom one.Check with german key words llike AH,WE.
Regards,
Madhu.

Similar Messages

How to get the pricing hierarchy based on the delivery date for sales order

Hi,
How to get the pricing hierarchy based on the delivery date for sales order other than system date.
My requirement is to get the Pricing hierarchy based on the delivery date other than system date.
Waiting for kind response.
Best Regards,
BDP

HI Sai,
please refer teh document already how to write FM based extration on generic extractors.
and here the logic to find the latest records values:-
-> get the data in an internal table
->Sort the internal table data based from date descending
-> Using READ statement , we can read the first record of the table which is nothign but your latest record.
Regards.
Sakthi

How system updating the delivery dates in sale order schedule line

Hello
i created a sales order with 2 line items. For the first line item the confirmed delivery date in the schedule line is 06.02.2012 and for the second line item the confirmed delivery date in the schedule line is 14.02.2012 . Both the line items are third party items and the PR created against the line items in the sales order .
We created the PO with reference to the PR of the SO and we find there are different delivery dates coming in the PO document for the 2 line items . For the first line item the delivery date is coming as 14.11.2011 and for the second line item in the PO , the delivery date coming as 11.11.2011 . Firstly we are not understanding from where the delivery dates are picking in the PO.
Secondly , once we saved the Purchase order and once we come back to the sales order , the schedule line dates are getting changed automatically in the sales order . For the first line item in the sales order the delivery date is changing to 22.11.2011 and for the second line item in the sales order the delivery date is changing to 22.11.2011.
Now my question , is from where the delivery dates are updating in the Purchase order and once we save the purchase order how the delivery dates in the schedule line are getting changed .

Now my question , is from where the delivery dates are updating in the Purchase order and once we save the purchase order how the delivery dates in the schedule line are getting changed .
For third party processing, the delivery dates are updated in the purchase order based on the settings in the field Planned delivery time in the MRP2 view of the material master(defined in purchase info record in t.code ME11/ME12) and purchasing processing time defined in t.code OMEW. This means, since the date of PO created, it will take the days mentioned in the planned delivery time field and purchasing processing times to determine the delivery date, which will be copied into the sales order as delivery date. In your case, the purchase order delivery date is not copied into the sales order, hence you may need to check OSS note. How the PO is handled? Any confirmation control functionality is used?
Regards,

Update the pricing data from sales order

Hello Friends,
we use vk11 to create a combination for a particular condition type pricing so the same will be reflected when we create a sales order.
my requirement.
If the user makes any changes in the price for a paticular condition in the sales order thn the same should get updated in the masters so tht next time if i create sales order for the same combination it should reflect the updated price.
in simple terms i want to update master data for a particular condition if the user makes changes in sales order pricing.
Regards,
Sunny

Dear Sunny,
in simple terms i want to update master data for a particular condition if the user makes changes in sales order pricing.
It is not possible to update condition record when you change the price in the sales order.
I hope this will help you,
Regards,
Murali.

Update Material Availability Date for Sales Order having a Delivery

Dear Gurus,
We have a bit out of the way scenario. There is a o/b delivery already added to a shipment. And then we receive a IDOC from external MES System (i.e. Production) with new material availability date. This new material availability date is updated on Sales Order. In short the order is delayed.
Current Solution:
In this case the user has to remove the delivery from the shipment manually. then the IDOC deletes the delivery and the updates the sales order with new date followed by creation of new delivery.
The business expects to updated the Sales Order material availability date without changing Shipment / delivery. Any solution?
Current solution has to be changed as for Shipment purpose changes are made to delivery which are lost when the delivery is deleted.
Edited by: abhishek singh on Feb 3, 2012 10:21 AM

hi
in this case you have to adopt the business process change.
you have to update the EDI first and then you create delivery.

How to see archive data for Sales order

Hi all,
I am working on PS , network is created with sales order 10911. the components are added while sales order created, but after that someone deletes the sales order, because now it is showing oder does not found, where i get the entreis for sales order.
Regards,
Khushi.

Hi Khushi,
To see the archived data for sales order , go to transaction code SARA.
Choose object name as SD_VBAK.Click READ.
It will show a screen giving a name of program and option to execute in background or foreground.
It will help you to get information about archived sales order data.
Hope it helps you.
Thanks,
Sarita singh Rathour
Edited by: Sarita Rathour on Aug 28, 2009 7:46 AM

Upload the data for sales order using BAPI

hi experts,
how to upload the data for sales order using BAPI.
what is the FM?
it would be much helpful if i have the sample code as i am very new to BAPI.
thanks and Regards
Shyam

Hi Shyam
Its very useful for u
BAPISDORDER_GETDETAILEDLIST
BAPI_ACC_SALES_ORDER_CHECK
BAPI_ACC_SALES_ORDER_POST
BAPI_ACC_SALES_QUOTA_CHECK
BAPI_ACC_SALES_QUOTA_POST
Reward all the helpful answers..
With Regards
Navin Khedikar

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

How to update the condition price in sales order while creating the invoice

Hi,
How to update the condition price in the sales order to carry out the new price while creating the invoice?
While creating the invoice it should update the condition price in sales order.
Thanks,
Balaram

No, pricing is not there in delivery.
I found an exit for VF01transaction where we can update the price in order.
Can you please tell me how to update the price if I have the order, material numbers and conditions number?
Thanks,
Balaram

Quality inspection for the items issued for Sales order

Hi, How to map the qc for the items issued for sales order?

Dear Yadav,
-Activate insp type 10 in the Material Master-QM view insp setup (MM01)
-Create Inspection plan (QP01) with usage as Goods issue & assign Insp characteristics
-Create Sales order (VA01)
-Delivery against the Sales order (VL01N) or through sales order menu. Delivery Insp lot gets created after Delivery is made.
-Do results recording and take usage decision (QA32)
Note:
-This inspection is non stock relevant inspection. There will be no stock posting through Quality Management.
-Post Goods issue in the delivery can be made only after taking the usage decision.
Regards,
Keerthi.

Problem in updating Billing plan while changing Sales order

Hi All,
        I am using the BAPI 'BAPI_SALESORDER_CHANGE' to change a Prepaid Sale order.After calling this BAPI ,I am calling the function module <b>'BILLING_SCHEDULE_SAVE'</b> to update the Billing plan of the changed Sale order(Billing plan dates for Billing type ZF1 are changed).
     The updated date values are getting reflected in the screen when I view through the transaction VA02 and the values are also updated in FPLT table but the values are not getting reflected in the table VKDFS.
   Since the values are not getting reflectedin the table VKDFS the billing date is not correct while we view in the transaction VF04.
   Please provide your valuable suggestions for updating the Billing date in VKDFS table.
    Thanks in advance for your help.
Thanks and regards,
Siva

Hi,
I had the same problem. Here is an example code to resolve it:
REPORT ytestfg.
DATA: i_bsid LIKE bsid OCCURS 0,
      i_bsid2 LIKE bsid OCCURS 0.
TABLES: bsid.
DATA: doc     LIKE     vbak-vbeln,
      pos(6) TYPE n.
DATA e_fpla     LIKE     fpla.
DATA e_fplt     LIKE     fpltvb OCCURS 0 .
DATA: zfpla     LIKE     fplavb OCCURS 0,
zfplt     LIKE     fpltvb OCCURS 0.
DATA zfplt2     LIKE     fpltvb OCCURS 0 WITH HEADER LINE.
doc = 'G03060619'.
pos = '000010'.
CALL FUNCTION 'SD_SALES_DOCUMENT_READ'
EXPORTING
    document_number = doc.
CALL FUNCTION 'SD_SALES_BILLINGPLAN_READ'
EXPORTING
    i_vbeln                = doc
    i_posnr                = pos
IMPORTING
    e_fpla                 = e_fpla
TABLES
    e_fplt                 = e_fplt
EXCEPTIONS
    no_billingplan_allowed = 1
    no_billingplan_found   = 2
    OTHERS                 = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Read the billing plan
CALL FUNCTION 'BILLING_SCHEDULE_READ'
EXPORTING
    fplnr          = e_fpla-fplnr
I_VFKDAT       =
I_BFKDAT       =
TABLES
   zfpla          = zfpla
    zfplt          = zfplt
Upddate the ZFPLT2 table with the new values
MOVE zfplt[] TO zfplt2[].
READ TABLE zfplt2 INDEX 1.
zfplt2-afdat = '20080927'.
Very important to set field updkz = 'U' ***
zfplt2-updkz = 'U'. "--> UPDATE!!
MODIFY zfplt2 INDEX 1.
CALL FUNCTION 'BILLING_SCHEDULE_SAVE'
TABLES
    fpla_new = zfpla
    fpla_old = zfpla
    fplt_new = zfplt2 " --> NEW
    fplt_old = zfplt.
CALL FUNCTION 'SD_SALES_DOCUMENT_SAVE'.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
Regards,
Edited by: PHO_BA on Mar 9, 2009 5:28 PM

CRMXIF_ORDER_SAVE_M01-IDoc Sample data for sales order in CRM.

Hi Friends ,
I am usig the IDoc CRMXIF_ORDER_SAVE_M01,I could able to save the Order in CRM,but the values of partners, Sales area,PO Category,Customer Po details and the material detail are not available in the created Sales order,though I am pasing them.
Are there any mandatory fields/qualifiers I am missing
E101CRMXIF_ACTIVITY - for the PO Category
E101CRMXIF_PARTNER - for the Partners
E101CRMXIF_ORGMAN - for the Sales Area
E101CRMXIF_SALES - for the Customer Po details
E101CRMXIF_BUSTRANS_ITEM - for the Material details
Can any one share a sample IDoc segment fields with the data.
I greately appreciate your early help.
Thanks
VJ

Hi Vijay,
Here what I would do to analyse this further. Please try to create the saem order directly in CRM with the
same masterdata and test the result. There might be a partner procredure or accesses which cna interfere.
If this is not helpful please let me know the error message ID and number you are getting in CRM as well.
Best regards
Christophe

Closing Date for Sales Order?

Hi, is there a way to get the closing date for a sales order? I've noticed the CloseDte on ORDR is always null.
If not, is there a way I can catch a close event in SP_TransactionNotification?
Thank you,
Jose

Hi Jose,
CloseDte on ORDR is not updated when the order closed. It is not possible to catch a close event in SP_TransactionNotification either because this SP can only be used for Blocking the transaction.
The best work around is through ADOC table.
Thanks,
Gordon

Update KOMV-KBETR field for sales order and billing

I would like to update the KOMV-KBETR (condition amount or percentage) under condition tab for both Sales order and billing.
example:There are two condition types ZA00 and ZB00 and need to get the KBETR value from ZA00 and add it to KBETR value of ZB00 and update the sum in KBER value of ZB00.
1. creation of sales order & billing.
2. Change of sales order & billing.
3. For single & multiple line items in both sales order & billing.
4. during updation of price in the change mode of sales order & billing.
5.When user click on Update button in the condition tab(i.e., when clicked on Carryout new pricing)
I tried with the VOFM routine but as the routine is triggering multiple times the sum is calculated again and again.For that I set flags also.It is working for sales orders but for billing creation the field XKOMV-KBETR is cleared after this routine.
So I would like to know are there any EXITS for this scenario or any one entountered the similiar issue which I am facing.

Hi Brad,
It is an Client requirement.So need to do the addition of that condition types.
Can you please let me know the configuration point where we can do it and the condition type which we need to update the Rate/Amount value.ie., KOMV-KBETR is and Price list value and not the subtotal one.
Thanks,
Srilakshmi Lagisetty.

Update payment card details for sales order

Hi all,
Is there any function module or bapi which can be
used to update the payment card details for a sales order
The bapi_salesorder_creatfromdat2 is having the structure
CCARD which takes in this details , but what I really want is to change the already created sales order. The bapi for sales order change is not having any structure which allows passing this details.
Please can anybody give some inputs on it.
Regards,
Shibu Mathew.

Hi Anurag,
Thank you very much for the answer..
I too found it as i was digging through the
BAPI_SALESORDER_CHANGE.
One's again thanks for the solution.
Regards,
Shibu Mathew.

Problem in updating the partners data for sales order

Similar Messages

Maybe you are looking for