Sales order IDOC process Using FM J_4A_IDOC_INPUT_ORDERS

Hi ABAP gurus,
i am working on Sales order creation using IDOC .
while i am Filling idoc i am filling reference document number and
item number .(VGBEL and VGPOS). but when i process idoc i am not getting reference document number at item level. here we processed idoc using FM J_4A_IDOC_INPUT_ORDERS.
Please suggest me which segment do i neeed to fill for getting reference document number at item level .right now i am using E1j3p02 segment.
or do i need to implement user exit for this.
thanks,
Neo.

Hi Shareen Hegde
To create Inbound...idoc
Use the Function Module in you Program : IDOC_INBOUND_WRITE_TO_DB to create the Inbound idoc
Pass the Control record and Data record in FM.....
Use Message type : Orders
IDoc type : Orders01 or 02 or 03 or 04 or 05 .... which ever suite for your requirement....
Process Code : ORDE
When ever your custom program for creating the inbound sales order with runs .....
it call the internally FM IDOC_INPUT_ORDERS to create the Sales order...
or
If you are getting the inbound idoc from subsystem .....then check you partner profile ,Message type ed and Process code is correct or not....
I hope this resolves your issuse..
Ramesh

Similar Messages

Sales Order IDOC creation using IDOC_INPUT_ORDERS

I am trying to create a Sales order IDOC (Inbound) from a flat file using the FM - IDOC_INPUT_ORDERS .
I am able to create the sales order. But I don't see the idoc getting generated anywhere.
I see the import parameter - DOCUMENT_NUMBER coming blank. Why is the IDOC not getting generated ?
Any tips will be useful ?
Can we create Inbound SAles Order IDOC using 'MASTER_DISTRIBUTE_IDOC' FM ?
THanks.

Hi Shareen Hegde
To create Inbound...idoc
Use the Function Module in you Program : IDOC_INBOUND_WRITE_TO_DB to create the Inbound idoc
Pass the Control record and Data record in FM.....
Use Message type : Orders
IDoc type : Orders01 or 02 or 03 or 04 or 05 .... which ever suite for your requirement....
Process Code : ORDE
When ever your custom program for creating the inbound sales order with runs .....
it call the internally FM IDOC_INPUT_ORDERS to create the Sales order...
or
If you are getting the inbound idoc from subsystem .....then check you partner profile ,Message type ed and Process code is correct or not....
I hope this resolves your issuse..
Ramesh

Sales order IDOC process

Hi Guys
I need the ALE/IDoc entire process to receive sales order master data from clients
Also IDoc using BADI when a sales order is created please help, I have not worked with IDOCS before.
Points will be rewarded
Thanks in advanced
Regards

One way to do what you have described:
1.     Set the partner profiles for the inbound ORDERS message to u201CTrigger by background program.u201D This will put the inbounds into status 64 until they are selected for processing by a user.
2.     Write a custom report to list status 64 ORDERS according to relevant control record data (like sender and date received).
3.     Build into the output screen of the custom report the ability to u201Cdrill intou201D an IDoc and display the information that your Sales folks need to make a decision.
4.     Build two command button actions into the u201Cdrill downu201D screen
u2022     Process the IDoc (using a call-transaction to standard program RBDMANI2).
u2022     Reject the IDoc and change the status to something other than 64 (like 67 or 68).
May I suggest another approach?
Configure the document type that gets created by the ORDERS IDocs to default with a delivery block upon creation. Then your Sales folks can review it and decide whether to remove the block or reject the entire order.
Regards,
zKen

No batch input data for screen SAPMSSY3 0131 in Sales order IDOC

I am processing Sales order IDOCS in status 64 using RBDAPP01 .Some of them error out to status 51 with the message -
No batch input data for screen SAPMSSY3 0131 .
I know the standard IDOC inbound process tries to simulate the posting in a BDC like process.
Now, I went to we19 and the screen hangs up in a pop up in the partners tab with partner type 'WE' and my shipto (which is actually filled in the IDOC), missing..upon repeatedly hitting enter, it goes thru and an idoc is posted in status 53. But still unable to get through the root of this issue.
Any, insight will help.

Hi,
I think the pop-up is generated through and user-exit for which recording is missing. This is why your idoc stays in status 64...
Handle the screen recording in the user exit IDOC_INPUT_ORDERS
user exit routine
PERFORM customer_function_dynpro.
FORM CUSTOMER_FUNCTION_DYNPRO.
CALL CUSTOMER-FUNCTION '002'
    EXPORTING DXVBAK   = XVBAK
              DVTCOMAG = VTCOMAG
              DLAST_DYNPRO = LAST_DYNPRO
              DXMESCOD = IDOC_CONTRL-MESCOD
    TABLES    DXBDCDATA = BDCDATA
              DXVBAP    = XVBAP
              DXVBEP    = XVBEP
              DYVBEP    = YVBEP
              DXVBADR   = XVBADR
              DYVBADR   = YVBADR
              DXVBPA    = XVBPA
              DXVBUV    = XVBUV
              DIDOC_DATA = IDOC_DATA
              DXKOMV    = XKOMV
              DXVEKP    = XVEKP
              DYVEKP    = YVEKP
    EXCEPTIONS
              USER_ERROR = 01.
Regards,
Krishnakumar

Segment for WBS element in Inbound Sales Order Idoc

Hi gurus,
I am trying to create an inbound idoc for sales order ' VA01'. I need to populate WBS element in the item level under Account Assignment Tab. I am using ORDERS05 basic type. Please help to find which segment to use for WBS element. Waiting for your reply. Please help.
Regards,
Satyajit

Hello,
        As far as I know, there is no Segment / Field definition in ORDERS05 for WBS Element as it is not mandatory information to be filled in order for the Sales Order to be Complete. So, you need to create an Extension of the IDoc Type ORDERS05. For your requirement, here is the Approach I have.
1. Create an extension for IDoc Type ORDERS05 to ZORDER05 with a Custom Segment Z1EDP01 in which you'll have the Custom Field Name VBAP-PS_PSP_PNR which is the WBS Element field in VBAP Table.
2. Now, use the Customer Exit EXIT_SAPLVEDA_001 in the Enhancement VEDA0001 in which you can actually populate the Field WBS Element that would be already available in the Inbound IDoc to store it in a Work Area. As you are aware, you'll need to create a Project in CMOD for the same.
3. Export the same to some MEMORY ID 'XXX'.
4. Come back to the Selection Program for ORDER05 which is IDOC_INPUT_ORDERS in which you'll find the below CASE Statement.
    CASE xaprau.
          WHEN ' '.
            PERFORM call_va01_new_orders USING ok.
          WHEN 'Q'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Angebot
call transaction Order Entry VA01 with refer to quote number.
            PERFORM call_va01_new_orders_angbt USING ok.
          WHEN 'C'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Kontrakt
call transaction Order Entry VA01 with refer to contract number
            PERFORM call_va01_new_orders_contk USING ok.
          WHEN 'L'.
5. Now, since our Standard Order Type (VBAK-VBTYP) is 'C',
    we'll have to choose the Subroutine for the 'C' Option.
6. In this Subroutine, there is another Subroutine va01_dynpro_kopf_kaufmann_kde2 which is for populating Custom Dynpro Fields for the Sales Order. So, we need to choose the same Subroutine inside which we have to Create an Enhancement Implementation.
7. In this Enhancement Implementation (Implicit), we have to IMPORT the value of the WBS Element which was exported in the Customer Exit.
8. Check if it is initial. If it is not, then Call the Perform as below.
     IF NOT WA_Z1EDP01 IS INITIAL. "Checking if the Segment
                                                       " is Empty
   PERFORM DYNPRO_SETZEN USING 'COBL-PS_POSID' WA_Z1EDP01-ZZWBSELEMENT.
ENDIF.
9. Since the Sales Orders are posting using BDC here, by calling the above Subroutine DYNPRO_xxx, we are appending our Custom Segment / Field value to the BDC_DATA table.
10. In Step 8, I've given the Notation for Work Area. It will also be applicable when there are multiple Line Items. All you have to do is to EXPORT an Internal Table instead of Work Area and use the same here for each Line Item.
11. I've given you above procedure because I've worked on similar requirement in which I had to populate the Special Processing Indicator instead of WBS Element.
Hope it would be helpful for you.
Thanks and Regards,
Venkat Phani Prasad Konduri

Creating inbound Sales Orders IDOC within SAP

Hi,
I receive a flat file containing sales order information. I would like to create inbound Sales Order IDOCs from this flat file. I know I can use BAPI_SALESORDER_CREATEFROMDAT2 to create sales orders however I would like to retain the benefits of IDOCs e.g. error retention and re-processing.
There are a number of functions MASTERIDOC_CREATE* to create various IDOCs but I can't seem to find one for message type ORDERS. I know I can create a 'Z' version but would like to avoid that as much as possible as development budget is tight.
Any help would be greatly appreciated in the form of reward points.
Thanks and regards,
Liam

Hi,
Can u tell me the steps to create a sales order using idoc, i've created a bapi but thats a temprory use. I wanted to created a sales order automatically when a purchase order is saved.
Please let me know if u can help me, i wanted to do it using idoc
Regards
Sanju

Sale order costing process : Help required

Hello All,
Belatted Happy New Year 2011 to all.
I have a question related to Sale Order Costing. It goes like this,
My client is into Pipe coating business who receives the pipe from the customers, coats it as per there requirements and despatches it thereon. There is no concept of FG here as its only the service he is doing on it and also when he receives the pipe there is no raw material cost on it. Raw materials for him would be chemicals etc which he uses to coat the pipe.
And also this demands variant configuration from SD and PP angel.
As this scenario is customer specific, it demands Sale Order based costing(Sale order cost estimate).
My doubt is, how the sale order costing process goes with.
In general scenarios, Make to stock, we use production order based costing where standard cost estimate is calculated for planned cost and actuals are incurred on PO settling the variance to COPA
Similarly how the costing goes with if Sale order cost estimate is used. What i think is, here instead of Standard cost estimate for plan, we will go with Sale order cost estimate at sale order level, and incur actual cost at production order and settle the cost of Production order to Sale order. Correct me if i am wrong, and request you ppl there to explain me the process of costing in the scenario said above.
apart from that, my client wants the flexibility to change the cost estimate at quotation level.
Please suggest me with solution explaining the process of costing here.
Thanks in advance,
Ravi Kumar

Hi Ravi
Your understanding of the scenario is very much right...
In your case, you need to have sales order as cost object...
Process
Your stock would be non valuated stock, because the FG is not your stock.. You are just doing a service
Based on the characteristics chosen in the Sales orders, system would determine the Sales order BOM
Based on sales order BOM, Sales order cost estimate would be calculated....
You would receive the Customer pipe in your stock against the sales order... It would be a non valuated GR... You can track the Qty only
Sales order would trigger a production order... The prod order can have its planned cost, which is only for information sake
The Customer Pipe, Chemicals would be issued to prod order to coat the pipe... And also Labor/machine hrs may be confirmed
There after your production order would be settled on Sales order
Then you would do PGI (Post Goods Isue).. This will not trigger any accounting doc
Then you do billing... The sales revenue would be posted on the sales order
Then you settle the sales order to COPA.. This will close the cycle
Configuration
The IMG Settings required would be as below
1. You would use account assignment category (AAC) E
2. Create a Requirement class with
a. AAC = E.... (Means sales order is CO Object)
b. Valuation Indicator = BLANK (Means Non Valuated Stock)
c. Costing ID/Costing Method = As per your choice to calculate the Sales order cost estimate
3. Assign this req class to Requirement Type
4. Give this req type to your PP/SD team.. They would assign it to Strategy group / Item Category to determine it in the sales order
Regards
Ajay M

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

Sales order stock process

Hi All,
We are planning to implement sales order stock process. There is some confusion regarding the picking process of sales order stock. Can anyone help me in this matter, how to do picking for sales order stock item? Is this in the normal way or not?
Thanks,
Vijesh

Hi,
yes the stock is maintained for sales order and even blocked in MB1B using 412 -E ..in MMBE now the stock is showing as sales order stock .
this part is clear,
now the issue is regarding picking... how can we to picking process..can we do picking using sales order stock..it is because , in LS24 the stock is showing as E which is not in any bin locations.
In the normal process we are doing the picking from bin locations..
thanks to advise the picking process in sales order stock.
Best Regards,
Vijesh

Sales order details uploading using BAPI method in LSMW

Hi Guys,
Sales order details uploading using BAPI in LSMW, could you please suggest me, is any standard method or programs is available for this.
I have some queries about this.
1) One header line having multiple line items, in this case we able to upload use the LSMW method,
if possible please tell me the steps.
2) Do we need to do any config changes while uploading data?
3) Flat file should be which format.
4) Steps to process each step wise if possible.
Please help me
Thanks,
Gourisanakar.

Hi Gouri Sankar,
would you be able to upload the sales orders with multiple line items using BAPI LSMW?
if so could you plz suggest?
Thanks in advance.
Suresh/

Sales order reles process

hello guru's
i need sales order relese process.
how can i map in sap.
if know any one please help me?
regards
dharma

Hi Dharma,
There is nothing like release strategy for sales order. There is a release strategy for purchase order. A bit of search on sdn forum in MM section will help you a lot on this area.
For your reference, The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 0
1
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Sales Order iDoc from SAP SCM 7.0

Hi Experts
I have two question fro you guys.
1. Can we generate VMI sales order idoc from SAP SCM 7.0? I know is can generate xml message. If we can generate idoc for VMI sales order from SAP SCM , please give me some direction or path to explore.
2. Can I use idoc to to create to VMI sales order in ECC skiping CIF. But the changes in ECC to these order should use the CIF to update the VMI orders in SAP SCM.
Please share your experience on this.

Hi,
Did you set up this scenario? I want something similar, but I want an ERP order to be created. Do you know if that is possible? Do you have som tips?
regards Camilla

Sales order idoc error only on ORDCHG message type (ORDERS01)

Hi. I am adding segment E1EDK04 to our sales order idocs in order to pass tax jurisdiction code to R3. When I create the order (message type ORDERS), I am extracting tax jurisdiction code from the idoc and I am adding it to the ship-to address screen via a BDC table within user exit include zxvedu04. The new order gets saved with the TXJCD, and this works fine.
I am now testing maintenance scenarios. For ORDCHG message types, I am inserting the TXJCD within user exit include ZXVDBU02. The idoc processor abends in 51 status with message:
"Control data in the IDoc E1EDK04 has been transferred. Check data".
If I walk the same status 51 idoc through BALE without changing anything, I see the TXJCD get posted to the order, and the order is saved correctly the second time.
Does this mean I need to add something additional to the idoc control data on an ORDCHG or something?
Thank you.
Brendan

I was not able to get any farther on this. It would seem that when the idoc is processed in the foreground, something is being populated that is not present when the idoc come across to R3...
The thing is, when I walk through the idoc in the forground, there are no errors that pop up. I can save the idoc after foreground processing and it moves into 53 status.
Thanks for any ideas that you might have on how to gather more infromation.

How can we remove an unwanted # in sales order texts created using a bapiFM

Hi,
i've written the following code which splits the record fetched from apllication server and moves it into a workarea.
CONSTANTS:c_sep VALUE cl_abap_char_utilities=>horizontal_tab, "for separation
SPLIT wa_tab1-rec1 AT c_sep INTO wa_inf_itm-inf_vbeln
                                       wa_inf_itm-itm_number
                                       wa_inf_itm-material
                                       wa_inf_itm-req_qty
                                       wa_inf_itm-uom
                                       wa_inf_itm-amount_pr00
                                       wa_inf_itm-amount_pi02
                                       wa_inf_itm-amount_mwst
                                       wa_inf_itm-amount_vprs
                                       wa_inf_itm-currency
                                       wa_inf_itm-text.
Here c_sep will have a value '#' instead of 'space' in Flatfile from application server.
The field 'wa_inf_itm-text' though it doesnot contain any value in debugging, when the sales order is created using FM 'BAPI_SALESORDER_CREATE_FROM_DAT2' the item texts are having a # character at the end of the text if it has any text(when checked in va03--sales order item text) or if it doesnot contain any text ,then also # character is seen in texts.
Thanks & Regards,
Prasad Reddy.

hi
use
Replace all occurrence of '#' with space from .......
I think it will solve ur problem.
Rewards with point if helpful.
Regards
Santosh.

Error while creating sales order with ref using SD_SALESDOCUMENT_CREATE

Hi
I am creating sales order with reference using function module SD_SALESDOCUMENT_CREATE , while creating i am getting error
Document doesn't have document category even thougth i am passing document category in header as well as item lavel.
In VBUK table there is no value for VGTYP.
Can you please help me how to resolve it.
Thanks & regards
kiran

Problem resolved by passing REFDOC_CAT in the FM along with SD_DOC_CAT.
Thanks

Sales order IDOC process Using FM J_4A_IDOC_INPUT_ORDERS

Similar Messages

Maybe you are looking for