ME2O delivery

Hi,
I cannot post a delivery from ME2O.
The error message is:
Essential transfer parameters are missing in record: 000001
How can I solve this error ?
Regards

I think the shipping data is not getting determined properly, please check the configuration if it has been done correctly for the system to determine the shipping data
Check and Get back
Chandra Kiran

Similar Messages

ME2O Delivery created, but quantity?

Hi,
After we could sucessfully created delivery in ME2O base on the required quantity.
But for certain material has it's lot size while goods issue.
Is there any possibility to define the lot size when create delivery.
Thanks,
Steven

if you know the lot size then just enter the quantity of the lot size as your delivery quantity.
But I guess you want that SAP shall change the manually entered delivery quantity automatically according to your lot size, is that what you want?

Missing automatic valuation type in delivery ME2O

Hi SAP Gurus,
I'm trying to set a stock determination rule in a Subcontracting PO for materials having split valuation ("E" and "I"). I set everything about the final PO to choose the split valuation for components (it works good), I have a problem with the ME2O Delivery.
To do that I set into OSPX the stock determination item table, I linked the material and the movement (541) with the right stock determination group, the delivery item category with the stock determination rule.
When I create a delivery from ME2O it doesn't contain any Valuation Type and at the goods issue I must insert it manually.
Why isn't valuation type set automatically?
Thanks in advance for your replies!

Dear Prasad,
I've already done it for many movement type (e.g. 261, 301, 309, 311) and it works for all of them. The problem is actually just for the mvt 541. In particular, if I set the stock determination for this movement it does not determinate the valuation type and also, if I fill the field with valuation type "E" the system gives the follows error message.
E M7 071
Please enter a vendor for special stock O
Thanks in advande for your help.
Best regards,
Paolo

Po to inbound delivery

Dear friends
I have a scenario where i need to bring the master data text to inbound delivery text.what are the settings required.Is it possible?
Regards
Aaryabalaji

Hi,
This note should help to map the text determination procedure from the
purchase order in the system correctly.
The function 'Text from purchase order' is available as of Support
Package SAPKH46B32 in Release 4.6B and SAPKH46C23 in Release 4.6C.
The following consultation refers to Customizing as of Release 4.70 and
higher - transaction VOTXN.
However, it is also relevant for Releases 4.6B and 4.6C as of the
Support Packages mentioned above - transaction VOTX.
Customizing for the procedure texts from purchase order -> delivery
1. Delivery type definition
Define your own delivery type for texts from purchase orders.
Since preceding documents from purchase order and sales order may
exist for deliveries, a separate delivery type is required for a
correct text determination.
Create access sequences
Example: instead of replenishment delivery RD -> new ZRD
2. Text determination procedure definition
Use transaction VOTXN (VOTX) and create your own text procedure at
header level as well as at item level.
3. Creating access sequences
For the new text determination procedures, use text objects EKKO and
EKPO to create new access sequences.
If you only want to find texts in this access sequence that were
created manually in the purchase order, text object EKKO or EKPO is
sufficient.
Here you should also maintain the condition for both text objects.
These are
EKKO > '1'
EKPO > '50'
The maintenance of additional text objects in these access sequences
is also possible of course, for example, 'TEXT'.
4. Text determination procedure assignment
Assign the new text determination procedure of the header texts to
the new delivery type and the text determination procedure of the
item texts to the relevant item categories.
In VOTXN (VOTX), this assignment is required.
Check in case of errors in the texts from purchase order procedure
1. Check: Customizing
see above
2. Check: Table RVTXOBJ
If the system issues error message VC 220 'Only special text objects
are allowed' when you create the text objects EKKO and EKPO in
transaction VOTXN (VOTX),
check the table RVTXOBJ.
To do this, use transaction SE16 to go to the table.
If the entries EKKO and EKPO are missing there, execute the SDTXNMUP
correction report.
This reorganizes the table. -> For further information, see SAP Note
711954.
3. Check: Table TFRM
Use transaction SE16 to display the table contents of the TFRM table
and enter the 'TXNM' field value as the selection condition for the
group indicator for copying control (GRPZE).
Check if the entries for TXNM with grouping numbers (GRPNO) 018 and
019 exist > EKKO/EKPO.
table TFRM
GRPZE GRPNO BEZEI
TXNM 001 VBBK text name
TXNM 002 VBBP text name
TXNM 003 MVKE text name
TXNM 004 TEXT text name
TXNM 005 VBKA text name
TXNM 006 KNVV text name
TXNM 007 KNVK text name
TXNM 008 KNB1 text name
TXNM 009 KNA1 text name
TXNM 010 MATERIAL text name
TXNM 011 KNMT text name
TXNM 012 VTTK text name
TXNM 013 VBBK text name
TXNM 014 VBBP text name
TXNM 015 KONA rebate payment
TXNM 016 WBRK text name
TXNM 017 WBRP text name
TXNM 018 EKKO text name <<<<<<<
TXNM 019 EKPO text name <<<<<<<
If these two entries are missing, use the solution provided in
Note 524453. The cross-client RV80INCTFRM report generates the
missing entries in TFRM.
Then start the RV80HGEN report that regenerates the relevant
includes.
You must take into account the comments in the long text of Note
524453.
Caution:
You should NOT implement the two entries manually in the FV46TNNN
include
Since this is a generated include, these entries would be lost
during the next generation (RV80HGEN).
Then you would no longer find texts from the purchase order.
Implement Note 524453 instead.
For information about the function of transaction VOFM, see also
Note 327220.
4. Error message VC 220
You receive the above error message with the text
IMPORT_LOGFILE_KEY_TOO_SHORT in the REFER_TEXT_AFTER_COMMIT function
module.
This means that an error occurred in the interface of the update
module during the local update.
To solve the problem, carry out the RSVBLOCL report for the
REFER_TEXT_AFTER_COMMIT function module.
The update module is then regenerated.
Check for a data transfer routine:
Some customers still use the workaround from Note 53593 and have defined
their own text determination routine in transaction VOFM.
As of Note 417883, this is no longer required, since the text
determination procedure from the purchase order is now supported and is
set as default.
5. Transaction ME2O - (Delivery to provision of materials for
subcontract order)
The text determination for deliveries from the provision of
materials for subcontract order is not possible in the standard
system.

Shipping point determination - ME2O

I'm using ME2O for creating a delivery. I select a line and i press the Create delivery button. A popup appears but the filed Shipping point is empty. What configuration should i make to have a value in that field?
The shipp. points are assigned to the plants and the determination using the shipping conditions- loading grp-plant are already configured.
Thanks.

hi,
this is to inform you that,
ME2O - DELIVERY WITH REFERENCE TO SUBCONTRACTING.
Please check in IMG:
1. MM - Purchasing -> Purchase Order -> Setup Stock Transfer Order -> Define shipping data for plants
2. Select the plant and double click in Enter the following field the sales area for the same.
5.MM>Purchasing>set up Subcontractor order>assigning plants to the delivery document LB.
6.Have you created a Customer master record in the same sales area as Material and then assigned it to the Vendor Control data in CMR.
hope this clears this issue.
balajia

SD Delivery in Subcontracting

Dear Sapients!
All settings are maintained for Subcontracting delivery of RM to Vendor.
In ME2O:- Error is " Document is incomplete: You cannot save the delivery"
as in ME2O delivery sent in background so could not edit the document.
Anybudy knows to do this delivery in forground or how to solve the error.
Points to useful answers...
Thanks in advance

Hi
Pl. make sure you have done following settings for sending SC-Components to SC-Vendor using SD Delivery
1)     Extend your Material to your Plant (from which you have to Create Delivery to your SC-Vendor for sending SC Components) and in that Material master -- Sales Org/General Plant Data View - Maintain Loading Group and Transportation Group.and in Sales Org/Data:2 view Maintain Item Category group as NORM
2)     For That Sale areaCreate one Customer and in that Customer master  General data - Control data - Maintain your SC Vendor. (Here only you are linking your SC Vendor as Customersince while creating delivery to your SC Vendor from your Plant, you have to consider your SC Vendor as a Customer) And in Sales Area Data  Shipping Tab - Maintain Shipping Condition
3)     In OLME  PO - Set up STO -Define Shipping Data for your Plants - for your Plant from where you want to create Delivery to your SC VendorAssign this Sales Area..
4)     In OLME  PO  Set up SC Order - Maintain Delivery type LB for your Plant..
5)     In SPRO  Logistics Execution - Shipping  Basic shipping Functions - Shipping point Determination - Assign Shipping Point - There for your Shipping Condition and Loading Group Conditionfor your Plant from where you want to create delivery to your SC Vendor assign Shipping Point
6)     In SPRO  Logistics Execution - Shipping  Picking - Determine Picking Location - Assign Picking Location - There for your Plant, Shipping Point and Storage Condition( Which you will maintain in the Material masterGen.Plant Data/Sto. 1 View  Assign Storage Location from which you want to your SC Components to be picked during Delivery Creation
7)     Then Make sure In PO.whether shipping Tab has come in PO  Item details after creation of PO
8)     Then after Creation PO  in ME2O - Goto create Delivery - whether you are getting Shipping Point and if you save it Pl. Ensure Delivery No has been Created or notIf Delivery No has been created, then Do PGI in VL02N
If you have maintained the above settingsthen definitely you wont get any Error
Reward if useful
Regards
S.Baskaran

Header and Item Text

Hi
    Requirement is to copy the text from PO to Inbound delivery.Need how and what are all the step in configuration required?
-Prabu

Hi,
Solution
This note should help to map the text determination procedure from the
purchase order in the system correctly.
The function 'Text from purchase order' is available as of Support
Package SAPKH46B32 in Release 4.6B and SAPKH46C23 in Release 4.6C.
The following consultation refers to Customizing as of Release 4.70 and
higher - transaction VOTXN.
However, it is also relevant for Releases 4.6B and 4.6C as of the
Support Packages mentioned above - transaction VOTX.
Customizing for the procedure texts from purchase order -> delivery
1. Delivery type definition
    Define your own delivery type for texts from purchase orders.
    Since preceding documents from purchase order and sales order may
    exist for deliveries, a separate delivery type is required for a
    correct text determination.
    Create access sequences
    Example: instead of replenishment delivery RD -> new ZRD
2. Text determination procedure definition
    Use transaction VOTXN (VOTX) and create your own text procedure at
    header level as well as at item level.
3. Creating access sequences
    For the new text determination procedures, use text objects EKKO and
    EKPO to create new access sequences.
    If you only want to find texts in this access sequence that were
    created manually in the purchase order, text object EKKO or EKPO is
    sufficient.
    Here you should also maintain the condition for both text objects.
    These are
    EKKO   > '1'
    EKPO   > '50'
    The maintenance of additional text objects in these access sequences
    is also possible of course, for example, 'TEXT'.
4. Text determination procedure assignment
    Assign the new text determination procedure of the header texts to
    the new delivery type and the text determination procedure of the
    item texts to the relevant item categories.
    In VOTXN (VOTX), this assignment is required.
Check in case of errors in the texts from purchase order procedure
1. Check: Customizing
      > see above
2. Check: Table RVTXOBJ
    If the system issues error message VC 220 'Only special text objects
    are allowed' when you create the text objects EKKO and EKPO in
    transaction VOTXN (VOTX),
    check the table RVTXOBJ.
    To do this, use transaction SE16 to go to the table.
    If the entries EKKO and EKPO are missing there, execute the SDTXNMUP
    correction report.
    This reorganizes the table. -> For further information, see SAP Note
    711954.
3. Check: Table TFRM
    Use transaction SE16 to display the table contents of the TFRM table
    and enter the 'TXNM' field value as the selection condition for the
    group indicator for copying control (GRPZE).
    Check if the entries for TXNM with grouping numbers (GRPNO) 018 and
    019 exist   > EKKO/EKPO.
      > table TFRM
       GRPZE   GRPNO   BEZEI
        TXNM   001     VBBK text name
        TXNM   002     VBBP text name
        TXNM   003     MVKE text name
        TXNM   004     TEXT text name
        TXNM   005     VBKA text name
        TXNM   006     KNVV text name
        TXNM   007     KNVK text name
        TXNM   008     KNB1 text name
        TXNM   009     KNA1 text name
        TXNM   010     MATERIAL text name
        TXNM   011     KNMT text name
        TXNM   012     VTTK text name
        TXNM   013     VBBK text name
        TXNM   014     VBBP text name
        TXNM   015     KONA rebate payment
        TXNM   016     WBRK text name
        TXNM   017     WBRP text name
        TXNM   018     EKKO text name <<<<<<<
        TXNM   019     EKPO text name <<<<<<<
       If these two entries are missing, use the solution provided in
        Note 524453. The cross-client RV80INCTFRM report generates the
        missing entries in TFRM.
        Then start the RV80HGEN report that regenerates the relevant
        includes.
        You must take into account the comments in the long text of Note
        524453.
        Caution:
        You should NOT implement the two entries manually in the FV46TNNN
        include
        Since this is a generated include, these entries would be lost
        during the next generation (RV80HGEN).
        Then you would no longer find texts from the purchase order.
        Implement Note 524453 instead.
        For information about the function of transaction VOFM, see also
        Note 327220.
4. Error message VC 220
     You receive the above error message with the text
     IMPORT_LOGFILE_KEY_TOO_SHORT in the REFER_TEXT_AFTER_COMMIT function
     module.
     This means that an error occurred in the interface of the update
     module during the local update.
     To solve the problem, carry out the RSVBLOCL report for the
     REFER_TEXT_AFTER_COMMIT function module.
     The update module is then regenerated.
Check for a data transfer routine:
Some customers still use the workaround from Note 53593 and have defined
their own text determination routine in transaction VOFM.
As of Note 417883, this is no longer required, since the text
determination procedure from the purchase order is now supported and is
set as default.
5. Transaction ME2O - (Delivery to provision of materials for
    subcontract order)
    The text determination for deliveries from the provision of
    materials for subcontract order is not possible in the standard
    system.
- Sanjeev

Error while creating delivery using ME2O

Hi ,
We are using ME2O to creat delivery for subcontracting . But I click on "Create delivery" button there is an error message coming.
The error is as following:
Global official numbering: Input parameter incomplete
Message no. ICC_NUMBERING770
If anyone has any solution for it could you please let me know.
Thanks in advance.
Sonali.

Then make sure you have defined the LB in purchiasng for sub contract order
Or Goto this document and check that you have did all the config
External Subcontracting: Configuration Guide
1     Purpose
This configuration guide provides the information you need to set up the configuration of this building block manually.
2     Preparation
Before you start installing this building block, you must install prerequisite building blocks. For information on the prerequisite building blocks, see the Quick Guide for installing Chemicals (located on the DVD in BBLibraryDocumentationChem_Quick_Guide_EN_US.doc).
3     Configuration
3.1     Defining Shipping Data for Plant BP01
Use
The purpose of this activity is to maintain the shipping data for the supplying plant. (Shipping of the components)
Here you maintain the customer number of the receiving plant. This customer number is used in SD shipping processing to identify the goods recipient (ship-to party) if provision has been made in Customizing for a stock transfer to be carried out with an SD delivery
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management à Purchasing à Purchase Order à Set Up Stock Transport Order à Define Shipping Data for Plants
Transaction Code     SPRO
2.     On the Change View Stock Transport Order: Overview screen, select the production plant BP01 and choose Details.
3.     On the Change View Stock Transport Order: Details screen, make the following entries:
Field name     Description     User action and values     Comment
Plant          BP01
Customer no. - plant
Sales organization          BP01
Distribution channel          03     Intercompany
Division for intercompany billing          01     Product division 01
Language key          EN     English
4.     Save your settings.
Result
The shipping data for plant BP01 has been set.
3.2     Defining Delivery Type for Subcontracting
Use
The purpose of this activity is to assign Delivery Type for Subcontracting. For the supply of the input materials to be provided to the vendor (subcontractor) with respect to subcontract purchase orders, you have the option of creating an SD delivery from the list of stocks for a subcontractor.
In this step, you can specify a delivery type for the delivery of materials to be provided to the subcontractor.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing Purchase Order  Set Up Subcontract Order
Transaction Code     SPRO
2.     On the Change View Subcontracting Data: Delivery Type f. Provision of Material screen choose New Entries (F5) and make the following entries:
Field name     Description     User action and values     Comment
Supplying plant          BP01
Del. type f. subcon.          LB     SAP Standard
3.     Save your settings.
Result
The delivery type LB has been assigned.
3.3     Assigning checking rule
Use
The purpose of this activity is to assign the checking rule B = SD-Delivery to the MRP-Group 0000. This rule defines the checking procedure to be used for the availability check.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Production à Material Requirements Planning à MRP Groups à Carry out overall maintenance of MRP-Groups
Transaction Code     SPRO
2.     On the MRP-Group View choose Plant BP01 and MRP-Group 0000.
3.     On the View choose the Button: Check.rule dep.reqmt screen make the following entries:
Field name     Description     User action and values     Comment
Checking rule          B
4.     Save your entries.
Result
The checking rule B will be used for the availability check for the components during creating the LB-PO.
3.4     Defining item category determination in deliveries
Use
The purpose of this activity is to maintain the item determination for the delivery type LB and the Item category group VERP. (VERB is used in material master CH-4120)
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Logistic execution à Shipping à Deliveries à Define Item Category Determination in Deliveries
Transaction Code     0184
2     On the Change View Delivery item category determination: Overview screen copy the entry LB/NORM to LB/VERP. (The item category LBN will be found)
3     Save your settings.
Result
For materials with item category groups VERP you can create a delivery.
3.5     Assigning Picking Locations
Use
The purpose of this activity is to assign the picking locations to the combinations of shipping point and storage condition for every plant.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Logistics Execution à Shipping à Picking à Determine Picking Location à Assign Picking Locations
Transaction Code     SPRO
2.     On the Picking location determination screen, make the following entries:
Field name     Description     User action and values     Comment
ShPt     Shipping Point     BP01     Shipping point BP01
Plnt     Plant     BP01
SC     Shipping Condition     01
Sloc     Storage Location     0001
3.     Maintain another entry with the following values:
Field name     Description     User action and values     Comment
ShPt     Shipping Point     BP01     Shipping point BP01
Plnt     Plant     BP01
SC     Shipping Condition     02
Sloc     Storage Location     0002
5.     Save your settings.
Result
Storage locations have been assigned.
3.6     Searching Strategy for DL
Use
The purpose of this activity is to allocate the search procedure SD0001 to the order type DL.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Logistic General  Batch Management  Batch Determination and Batch Check  Batch Search Procedure Allocation and Check Activation  Allocate SD-Search Procedure/Activate Check
Transaction Code     SPRO
2.     Copy any entry for Sales Org. BP01, Distr. Channel 03 and Division 01.
3.     Change the Sales Doc.Type to DL and save your entry.
4.     Choose Save.
Result
The search strategy SD0001 has been assigned to the sales DL.
3.7     Activating Automatic Batch Determination for Delivery Item Categories
Use
The purpose of this activity is to allocate the automatic batch determination for appropriate delivery item categories.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Logistics General  Batch Management  Batch Determination and Batch Check  Activate Automatic Batch Determination in SD
Transaction Code     SPRO
2.     On the Choose Activity screen select Activate Automatic Batch Determination for Delivery Item Cat and choose Choose.
3.     On the Change View Automatic Batch Determination for Delivery Item Category screen, make the following entries:
ItCa     Description     AutBatchDt
LBN     "Mat. Provided" Item     X
4.     Choose Save.
Result
The automatic batch determination for delivery item categories has been activated for appropriate item categories.
4     Master Data
The following activities describe the master data required for this Building Block. The steps do not describe the transactions in detail but list the relevant transaction and the corresponding master data file. For more details on using the individual transactions refer to the Online Help in the system.
4.1     Creating Customer C-9000 for Subcontract Vendor (S-9000)
Procedure
1.     Access the activity using one of the following navigation options:
SAP Menu     Logistics  Sales and Distribution  Master Data  Business Partner  Customer  Create  Complete
Transaction Code     XD01
2.     Refer to the following file for details of the master data required: SMB15_SD_CUSTOMER_O034_J30_Q15.txt.
4.2     Creating Info Record CH-6120/S-9000
Procedure
1.     Access the activity using one of the following navigation options:
SAP Menu     Logistics  Materials Management  Purchasing  Master Data  Info Record  Create
Transaction Code     ME11
2.     Refer to the following file for details of the master data required: SMB99_ME11_O250_J01_Q15.TXT.
4.3     Creating Output Condition Record
Procedure
1.     Access the activity using one of the following navigation options:
SAP Menu     Logistics  Sales and Distribution  Master Data  Output  Shipping  Create
Transaction Code     VV21
2.     Refer to the following file for details of the master data required: SMB99_VV21_O229_J01_Q15.TXT.
4.4     Creating Quality Info Record
Use
The purpose of this activity is to create the quality Info records for subcontracting.
Procedure
1.     Access the activity using one of the following navigation options:
SAP Menu     Logistics à Quality Management à Quality Planning àLogistics Master Data à Quality Info Record: Procurement à Create
Transaction Code     QI01
2.     Refer to the following file for details of the master data required: SMB18_QI01_O002_Q41_Q15.TXT.
Result
The Q-Info record has been created.
4.5     Change material (add or replace values on Plant data/stor1 - Plant data/stor2.)
Use
The purpose of this activity is to add the storage condition to the appropriate material.
Procedure
1.     Access the activity using one of the following navigation options:
SAP Menu     Logistics à Materials Management  Material Master  Material  Change  Immediately
Transaction Code     MM02
2.     Refer to the following file for details of the master data required: SMB10_MM02_O011_P02_Q15.TXT.
Result
The storage condition has been added to the material master.

Error while creating the delivery in ME2O

Hi Gurus,
when the shipping depeartment is trying to create the delivery in ME2o to send the components for subcontractor, we are gettign the error message
Essential transfer parameters are missing in record: 000001
Please heklp on this one?
and as an ibservation i do see that this vendor is not setup as customer in vendor master in the purchasing data view of the vendor master. Is that the problem?
thanks
Anusha
Edited by: anusha vemulapati on Oct 21, 2009 6:31 PM

Yes, it might be one reason. It is mentioned in the error message (VL561).
Please create the ship-to party, extend it to the plant's sales area and assign it to the vendor master. /plant sales area is in V_001W_IV/
Please try it and if still you get the errors come back. (Please read the error message and check all the thing described there)
Regards,
Csaba

Delivery Split during creation of delivery using ME2O

The system creates two delivery documents for the same vendor while using transaction ME2O. There is no delivery split criteria defined in customizing

Hi,
Please check following note
546668 - FAQ: Delivery split when creating deliveries
Also check the note 355404 - Why was there a delivery split during creation?
in this note you have attached report ZLE_ANALYZE_DELIVERY_SPLIT run it in SE38,
You will come to know why two deliveries created
Thanks

Can't able to create delivery in ME2O

Hi MM Team,
one of my user is created a subcontracting PO and try to create a delivery in ME20 at that time he is getting a error message
(Essential transfer parameters are missing in record: 000001) also added to it the vendor is a new toller vendor, one thing i want to confirm with you guys in ME2O once i select the material and go for CREATE DELIVERY one screen appears asking for the input of vendor,material, shipping point ,plant, storage location ,batch and quantity here i dint give the input of storage location and batch either this could be a problem for the error.
Thanks
Karthikeyan.P

Hi,
Check points in these notes:
Note 458938 - FAQ: SC stock monitoring list, Transaction ME2O
Note 323991 - Availability check:Subcontract PReq subcontract PO componnts
Note 199360 - Creation of a SD delivery from TA ME2O
Note 519559 - FAQ: Goods issue for the reservation
and related notes
Regards
Eduardo

Delivery to Subcontracting Vendor in ME2O

Hi All,
I am working on a requirement where the Delivery needs to be created for the Purchase order in ME2O. Can someone help me out in this. I need the BAPI for doing this. It would be difficult to do with BDC. Please help
Thanks
Rashmi

Hi ,
Following is the sample code for creation of inbound delivery Using BAPI 'BAPI_DELIVERYPROCESSING_EXEC'
Which may be helpful.
PARAMETERS: p_vbeln LIKE ekko-ebeln.
DATA: BEGIN OF t_ekpo OCCURS 0,
ebeln LIKE ekpo-ebeln,
posnr LIKE ekpo-posnr,
kwmeng LIKE ekpo-kwmeng,
matnr LIKE ekpo-matnr,
werks LIKE ekpo-werks,
END OF t_ekpo.
DATA: t_request TYPE STANDARD TABLE OF bapideliciousrequest
WITH HEADER LINE.
DATA: t_created TYPE STANDARD TABLE OF bapideliciouscreateditems
WITH HEADER LINE.
DATA: t_return TYPE STANDARD TABLE OF bapiret2 WITH HEADER LINE.
SELECT ebeln posnr kwmeng matnr werks
INTO TABLE t_ekpo
FROM ekpo
WHERE ebeln = p_vbeln.
LOOP AT t_ekpo.
t_request-document_numb = t_ekpo-vbeln.
t_request-document_item = t_ekpo-posnr.
t_request-quantity_sales_uom = t_ekpo-kwmeng.
t_request-id = 1.
t_request-document_type = 'A'.
t_request-delivery_date = sy-datum.
t_request-material = t_ekpo-matnr.
t_request-plant = t_ekpo-werks.
t_request-date = sy-datum.
t_request-goods_issue_date = sy-datum.
t_request-goods_issue_time = sy-uzeit.
APPEND t_request.
ENDLOOP.
CALL FUNCTION 'BAPI_DELIVERYPROCESSING_EXEC'
TABLES
request = t_request
createditems = t_created
return = t_return
READ TABLE t_return WITH KEY type = 'E'.
IF sy-subrc = 0.
MESSAGE e208(00) WITH 'Delivery creation error'.
ENDIF.
COMMIT WORK.
READ TABLE t_created INDEX 1.
WRITE: / 'Delivery ', t_created-document_numb, ' created'.
Revrt back if any issues,
regards,
Naveen

Subcontracting - outbound delivery by ME2O for Multiple batch of 1MTR

**Dear Expert**
**Subcontracting -we want to send One material to Vendor for processing but this material having Multiple batches,In T-code ME2O we can enter only one Batch while creating delivery.**
**If we want to create Delivery for multiple batches of one material how we can send By ME2O ? is there any option to add multiple batches in ME2O**
**please reply as early as possible**
**Thanks & regards**
**Pash@SD**

Moved from sales forum. Please try to post the question in right forum so that you will get right solution.
thanks
G. Lakshmipathi

Delivery created through ME2O without PO number

As you are aware , you will not see PO number in Delivery if it is created through ME2O transaction. Could any one tell me how to get PO number in Delivery which is created by ME2O by some enhancemets/user exits etc.

ME2O is able to create deliveries to your subcontractor even when there is no PO, further you can deliver more quantity than the PO component quantity, and you can create one delivery to deliver components that are needed for more than one PO.
We often deliver a full truck load of components to a subcontractor, to save as much freight costs as possible. The subcontractor does not just a one-time subcontracting for us, he does it on-going.
because of this functionality SAP cannot establish a link between a PO and a delivery of components

ME2O transaction for delivery

HI,
I created a subcontracting PO . Then i need to do delivery through ME2O transaction. BUt i am not able to see the material for which i created the subcontracting Purchase order . PLease suggest what must be the problem . Is there any customising required for this .
Then i tried to do delivery for some other materail (which was previously present in the ME2O output) ,but i got an error that "Delivery type for that material is not set ..." . Please help in customising.
Waiting for your kind reply.
Thanks
Rohit Chavan

Hi,
For your 1st question, you have to check whether the BoM of the subcontracting part is maintained correctly, or not? Then run MRP for the subcontracting part again, maybe that will be okay!
For 2nd quesiton, if you want to create the delivery note to transfer the component stock to subcontractor via ME2O, you must do the following things:
Create a customer master data for the vendor, then assign the customer number to the vendor master data on the "Control" view;
Extend the "Sales Org data" and "Sales plant data" views in the material master data of the components.
After that, you can create the delivery note smoothly!
Good day
Tao

ME2O delivery

Similar Messages

Maybe you are looking for