Exit for Moving sales order data to Purchase order

Hi All,
I have a requirement where sales order data needs to transferred to Purchase Order.
We have few custom fields in EKKO table YY SHIP_DATE, YYMOL etc....When a sales order 3rd party is created a PR is automatically created.Based on this PR(Purchase Requistion) we are creating a PO(Purchase Order) and the custom fields needs to be populated from the sales order.
I have checked the Exit V45E0001 Update the purchase order from the sales order.Its of no use for us as all our fields are custom fields..Please help..
Thanks.

Hi,
>>>,if an error occurs while creating purchase order in ecc6.0
one very easy and all standard
set up workflow in receiver ECC and put a user group in WE20 for this logical system that receiver the sales orders
then in standard when there is an error with IDOC in the inbound
a mail will be send to the user group (and you can put as many users in this group as you wish) and they will all receive this error
this would be the easiest idea and all in standard
Regards,
Michal Krawczyk

Similar Messages

User exit for changing Sales order lines.

Hello experts ,
I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE" but it does not seems to do the job.
What is the name of user exit that i have to use for this task and which structure should be used, is it xvbap ? is it vbap ?
Thanks for the help.
Avi.

Hi,
find the user exit u required.
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
Best regards,
venkatawamy.y

For a Sales order, what is Actual Delivery Date to Customer?

Hi Experts,
I am an ABAP consultant. In a particular report, for a Sales order I am asked to display:
‘Delivery Create Date (LIKP-ERDAT)’,
‘PGI Date’,
‘Requested Delivery Date (VBAK-VDATU)’ and
‘Actual Delivery Date to Customer’.
And in addition, I also have to show:
‘No: of days between Order Create Date to Delivery Create Date’,
‘No: of days between Delivery Create Date to PGI Date’,
‘No: of days between Requested Delivery Date to Actual Ship Date’ and
‘No: of days between Order Create Date to Actual Ship Date’.
I’ve searched SCN for similar questions but I couldn’t get clarity. I’ll be very grateful if somebody can explain me how to find the ‘Actual delivery date to customer’ and what is the difference between this date and ‘Billing date’. Also, please explain, the difference between ‘Delivery Create Date’ & ‘PGI’?

Hi Rashmith,
It seems the report is related to delivery. Below is the explanation for the different terms you mentioned in your question.
Delivery Create Date (LIKP-ERDAT)---- when a delivery is created with or without reference of an order system writes the date of creation time of creation and created by in the header data. Creation of delivery does not means that goods are dispatched. There are many steps further after a delivery is created before goods are dispatched. For example I have created an order, created delivery on 01.01.2014; delivery date will always be 01.01.2014.
PGI Date (LIKP-WADAT_IST)------ Post goods issue date is the date on which goods move out of the company to carrier. This is the last step of delivery. When delivery is created system derives different dates of planning; at this stage it will determine the planned PGI date (LIKP-WADAT) and when actual PGI happens system writes the date in LIKP-WADAT_IST which is actual goods issue date.
Requested delivery date (VBAK-VDATU)------When order is created for a customer he asks for a material, a quantity and a date on which he wants the goods. This date on which customer wants the goods is called requested delivery date. Based on the requested delivery date system will check feasibility of delivering the goods on the requested delivery date based on the delivery scheduling.
You can get the RDD based on the below logic.
Input the delivery number in VBFA-VBELN and VBFA-VBTYP_V and get VBFA-VBELV.
Input VBFA-VBELV in VBAK table and get the value of VDATU.
Actual Delivery Date to Customer-----Actual delivery date is Actual post goods issue date (LIKP-WADAT_IST). This is the date on which goods are issued to the customer and customer is liable for billing for the goods dispatched.
Difference between the Actual delivery date (Actual goods issue date) and billing date.
Normally as per standard SAP, once goods are moved out of the company customer is liable to be for billing for the goods dispatched. So by default in standard SAP system copies the actual goods issue date (LIKP-WADAT_IST) as billing date (VBRK-FKDAT) irrespective of the date of creation of the invoice (If delivery is goods issued on 01.01.2014 and billing document/invoice is created today i.e. 14.04.2014, system by default will take 01.01.2014 as billing date). And this is the correct practice.
However if you want the current date as the invoice creation date instead of the actual goods issue date we can control it by copy controls feature given in SAP.
So based on the copy controls setting, it may be different from the actual goods issue date/ actual delivery date.

User exit to change item level data in purchase order

Hi,
Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirment is
For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked). now i cant use ME_PROCESS_PO_CUST because process_item wont get triggered if there is no change in itemlevel data.
Regards,
Rahul

Hi Rahul,
Probably EXIT_SAPLMEKO_002.
hope it helps,
Edgar

Help - User exit to change item level data in Purchase Order

Hi,
Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirement is For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked). now i cant use ME_PROCESS_PO_CUST because process_item wont get triggered if there is no change in item level data.
Thanks,
Rahul

Hi Rahul,
Probably EXIT_SAPLMEKO_002.
hope it helps,
Edgar

Report for viewing Sales order no against delivery date & actual GI date

Hi Experts,
Is there any report for viewing Sales order no against delivery date & *actual GI date*
Because in VL06F , i can only able to get planned GI.
Please guide regarding the same where i can get 'ACTUAL GI DATE ' against above combination .
Regards,
Sujit S.

dear Hrishi,
i followed your suggestion, but couldn't get desired results,
here i can get planned GI date, where i wanted to get Actual GI date for complted deliveries,
thanks for your valuable reply.
@ G. Lakshmipathi ;-
i think i will need to develop z-report for fetching the data from the tables
VBAK (to get sale order reference) and
LIKP (to get delivery and actual GI date)
thanks for your reply,
Regards,
Sujit

Purchase Item for a sales order but not on sales order lines

Hi,
Is it possible to purchase an item for a sales order but item is not actually on sales order? I know we can create PO through SO logistic tab and also through procurement confirmation wizard but these functionalities can be used to buy the item which is on the SO. The problem is that the item is not on SO. It's kind of hidden cost going against the SO.
Will be grateful for your help.
Thanks,
Kanu

Thanks Gordon. Ok I can add items to the PO. But will those items be costed against the SO? Because there is no SO number (POR1.BaseRef field) on that extra PO line.
I appreciate your help here.
Best Regards,
Kanu

Data Validation for SD Sales order and Deliveries

Hello All,
We activated the data flow for SD sales Order and Deliveries for Infocubes 0sd_co4 and 0sd_c05 and there correspoding datasources.
I have 2 queries
1. How to validate data for BI SD sales order with ECC.
2. How to validate data for BI SD Deliveries data with ECC.
Kindly help, <removed by moderator>.
Thanks,
Rakesh.
Edited by: Siegfried Szameitat on Jun 21, 2011 12:51 PM

Hi Rakesh,
You have to check the tables in R3 and then compare with the Datasources in BW.
For Examples
VBAK table in R3 for Sales Order on BW-2LIS_11_VAITM
VBRK table in R3 for Billing iin BW-2LS_13*
Check for that day how many sales order were there in VBAK table and there in BW.
Rgds
SVU123
Edited by: svu123 on Jun 21, 2011 8:19 PM

Extracting material classification data for given sales order

Hi Experts,
Requirement is I Need to display a report with material and its characteristics values for given sales order. Please let me know if there is any FM/standard tables involved to display the below fields.
Sales order number, Sales order line item number , Material number , Characteristic Name(ATNAM),Characteristic description(ATBEZ),Characteristic Value(ATWRT),Characteristic value description(ATWTB).
Thanks & Regards,
Pavee.
Moderator message: "spec dumping", please work yourself first on your requirement.
Edited by: Thomas Zloch on Oct 14, 2011 1:30 PM

Hi Keshav,
Thanks for spending your precious time in replying to my thread.
I did a search before posting, I got an FM which is we cannot use due to performance issue.
Thanks for letting me know that sales order has material and material has characteristics,
But For each characteristics that material has we will have several values, you will be selecting whichever is appropriate based on the requirement.
If you know the answer pleases post. I have enough patience to wait for answers from other experts.
Thanks
Pavee.

User-Exit for changing Sales Document Number - Urgent

Hi Experts ,
                 Please suggest me the <b>User Exit for changing Sales Document Number.</b>
thanks,
Jayesh<b></b>

hi jayesh,
chech this exit-----EXIT_SAPFV45S_002.
this exit's description says " Change Sales Document Using Configuration".
Other available exits are
SDAPO001            Activating Sourcing Subitem Quantity Propagation
SDTRM001            Reschedule schedule lines without a new ATP check
V45A0001            Determine alternative materials for product selection
V45A0002            Predefine sold-to party in sales document
V45A0003            Collector for customer function modulpool MV45A
V45A0004            Copy packing proposal
V45E0001            Update the purchase order from the sales order
V45E0002            Data transfer in procurement elements (PRreq., assembly)
V45L0001            SD component supplier processing (customer enhancements)
V45P0001            SD customer function for cross-company code sales
V45S0001            Update sales document from configuration
V45S0003            MRP-relevance for incomplete configuration
V45S0004            Effectivity type in sales order
V45W0001            SD Service Management: Forward Contract Data to Item
V46H0001            SD Customer functions for resource-related billing
V60F0001            SD Billing plan (customer enhancement) diff. to billing plan
Enter these exits name in SMOD transaction and select components. u can find all the user exits available for this exit name.
Reward me if useful..........
Harimanjesh AN

What's the name of FM for getting Sales Order Header / Item Status info

Hello All:
Do you know what's the name of Function Module for getting Sales Order Header / Item Status Overview ? Any sample code will be very much appreciated.
Basically, I am trying to create a Webpage where user can enter the Sales Order document number and will return the Sales Order: Status Overview.
Thanks,
Dipankar Biswas

Thanks everybody ! Appreciate for your prompt response. I was also looking for some sample code, and I did find some on. And here is one. I still have to try the code, but here is for all your reference:
*& Report ZBAPI_SALESORDER_GETSTATUS *
*& Read and Display the Sales Order Items and Status of the Order *
REPORT zbapi_salesorder_getstatus NO STANDARD PAGE HEADING LINE-SIZE 200 LINE-COUNT 33(3).
TABLES: vbap. "Sales Document Item Data.
DATA: wa_bapireturn TYPE bapireturn,
wa_bapisdstat TYPE bapisdstat,
it_bapisdstat LIKE STANDARD TABLE OF wa_bapisdstat.
TYPES: BEGIN OF ty_mat_name,
matnr TYPE makt-matnr,
maktx TYPE makt-maktx,
END OF ty_mat_name.
DATA: wa_mat_name TYPE ty_mat_name,
it_mat_name LIKE TABLE OF wa_mat_name WITH KEY matnr .
PARAMETERS: p_vbeln LIKE vbap-vbeln DEFAULT 5573.
START-OF-SELECTION.
SELECT matnr maktx FROM makt INTO TABLE it_mat_name.
CALL FUNCTION 'BAPI_SALESORDER_GETSTATUS'
EXPORTING
salesdocument = p_vbeln
IMPORTING
return = wa_bapireturn
TABLES
statusinfo = it_bapisdstat.
IF wa_bapireturn IS INITIAL. " Successful Execution.
WRITE: / 'Document No: ' COLOR 1, 20 'PO Number : ', 40 'Status' , 50 'Delv.Stat',60 'Item No', 80 'Material', 90 'Material Description', 130 'Net Price' COLOR 2.
ULINE.
LOOP AT it_bapisdstat INTO wa_bapisdstat.
WRITE: / wa_bapisdstat-doc_number. " Sales Document Number.
READ TABLE it_mat_name INTO wa_mat_name WITH KEY matnr = wa_bapisdstat-material.
WRITE: /20 wa_bapisdstat-purch_no, " Customer Purchase Order Number
40 wa_bapisdstat-prc_stat_h, " Processing Status
50 wa_bapisdstat-dlv_stat_h, " Delivery Status
60 wa_bapisdstat-itm_number, " Item Number
80 wa_bapisdstat-material, " Material
90 wa_mat_name-maktx, " Material Description
130(10) wa_bapisdstat-net_price. " Net Price
CLEAR wa_bapisdstat.
ENDLOOP.
REFRESH it_bapisdstat[].
ELSE.
WRITE: wa_bapireturn-message.
ENDIF.

Transaction code for Open sales order other than VA05

Hi all,
Can any one tell me what is transaction code for open sales order other than VA05.
Please help me .
Thanks & Regards ,
Srikanth P.

Hi Srikanth,
You can try below options.
1- VA05N - This can be run for multiple sold to party & multiple material, etc which was not in VA05. But this doesn't have all columns in VA05 report.
2 - You can check the sales order tables from transaction SE11 or SE16N
Try with below tables for your requirement.
Sales order Header data - VBAK
Sales order Item data - VBAP
Schedule Line Data - VBEP
Business data - VBKD
Status header - VBUK
Status items - VBUP
Best regards,
Anupa

Table for Open Sales Order Quantity

Hi
After creation of partial deliveries for a Sales Order , in which table open Sales Order quantities will be stored?
We are using in Material Master Avilablity check as 'KP- No check'.
in VBBE & VBBS table no data is there
where it will store can any plz guide me
Prasad

Hi prasad
1st of all as you are using KP no check availability check doesn't happen.
Check , VBEP table which is sales doc schedule lines and ,VBEH table is for schedule line history.
check in VBFA table sales doc flow
Hope these table will help you
Regards
Srianth

How to create a single delivery for two sales orders?

Hi Experts,
I need to create one delivery for two sales orders. But it fails.
The route, shipping point, ship to party are same for both orders but INCOTERMS are different.
Delivery date, Good issue date, loading date,material availability date, transportation planning date for 1st order is 12/07/11 and for second order is 14/07/11.
I have created delivery on 14/07/2011 but the delivery is created for 1st order only, the second order is missing in the delivery.
It not happened because of incoterms.? different dates
Kindly help regarding this.
Thanks
Raghu

Prerequisite for Grouped delivery
1. Header data should be same like Inco terms,Payment terms
Go to VL10A
Enter the sales order Numbers and execute
Select the sales order Nos for the group delivery and select "Background" Tab in Tool Menu Bar
If delivery is created coloured line items will get generated
Check the log for delivery docuements
Check and confirm
Senthils

Credit Block for released sales order

Dear All,
I have got one issue. There is a sales order which was created earlier say 15 days back. It went into the credit block at the time of saving it. It was released through VKM3 too.
Now when i change any field in the sales order today, it is going into the credit block. We are not changing any value of any of the item. Just maintaining the Billing block in it or remobving the Billing block.
The number of days maintained in the OVA8 are 182. So as per the standard functionality it should not go into the credit block for any change in the sales order like changing the billling date or changing the billing block.
Can you please let me know what might be the reason for this sales order to go into the credit block..??? Any help is very much appreciated.
Thanks and regards,
Vishi.

Dear Vishi
Please check if you have checked the critical fields option.
Credit check against critical fields (fixed value dates)
The indicator controls the critical field check. If the field is selected, the system checks whether critical fields have been changed.
Use
If a check is carried out, the following fields are relevant:
Payment terms
Additional value days
Fixed value date
Note
Use this type of check for sales documents only.

Exit for Moving sales order data to Purchase order

Similar Messages

Maybe you are looking for