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

Similar Messages

Delivery Split during creation of delivery for STO

While creating a delivery for STO, delivery is being created for individual line items. On analysis of VL 033 message, I found that the delivery split is happening because of Function SH: Unloading Point.
The message is
<i>"delivery split due to conflicting header data (Function SH: Unloading Point: <-> UP0065)"
Item 000020 cannot be shipped in the same delivery with the other items in the document because the header data (Function SH: Unloading Point) is different. The Function SH: Unloading Point item field has the value UP0065, but in the delivery checked for concatenation it has the value .</i>
This unloading point has been maintained in the customer master data (and needs to be maintained).
I have also been told by my Basis consultant that note 842704 is not valid.
Why is this happening and how to prevent it.
Lakshman

Sorry... but I could not see either the delivering point or the unloading point in the material sales: general / plant view. Those fields are not visible on the screen. I could also not find them in the config (I was checking if they are suppressed).
Regards,
Lakshman

Finding out the Batch which is present during creation of delivery

Dear All,
I need to keep track of changes in batch during delivery. I can find out the change using change documents ( tables CDHDR and CDPOS ). The problem is it keeps track of batches only after the document is saved . If during creation the batch is changed , we are not able to see the initial batch , all the other changes can be tracked using change documents. How can we find out the batches during creation of delivery ( Is there any table which stores the batch no during delivery.
Regards
D. Mallick

This does not looks possible...Changes can only be tracked once they are saved.

Error during creation of delivery challan (VL01N) for batch

Hi,
At the creation of delivery challan during batch determination the system displays the message 'The material is not handled in batch'. Although we have despatched this material considering batch determination previously with all customisation.
Kindly revert back as soon as possible.
Regards,
Goraksh.

Hi Goraksh,
I think somebody removed the check box of "Batch" from material master.
Please check and revert.
Regards,
MT
Edited by: M T on Apr 29, 2010 4:28 PM

Inbound delivery split on creation

Dear colleagues,
I'd like to create a unique inbound delivery for different scheduling agreements but the system splits it into 2 different inbound deliveries.
Both purchasing documents have same header/item information.
Why is system acting like this? I use VL31N and I do select "Purchase orders" button on the top.
Thanks very much in advance.

I asked myself and I answer myself...system is creating different inbound deliveries because purchasing documents have different address information in EKKO-ADRNR.
That's a standard functionality added by OSS 667436 which modifies include LV50SF08.
In order to avoid this functionality it's possible to erase field XKOMDLGN-ADRNR_LI = "" at the beginning of include.
I hope it helps someone.
Thanks anyway,
Josep

Delivery Quantity change during creation of Delivery Document

Hi Friends,
   I have a requirement of creating a Partial delivery when not much stock is available.
   For this I am using a BADI 'LE_SHP_DELIVERY_PROC' method Save_Document_Prepare.
   I am changing the contents of CT_XLIPS-lfimg in the method and also keeping UPDKZ as 'I', but still
   the quantity is not changing.
Pls Suggest.
Arpit

Check, "Outline agreement message" in Document type details in VOV8- (eg: CQ- Quantity Contract) under Transaction flow view.
Use Indicator:A- Check at Header level.
Then system pop ups the message saying " Already Contract is open for this Customer" - ( Assume, SOld to party already have Open Contract)
similarly, for Material, for this you should use Indicator" B- Check at Item Level.
Hope it helps

Error during creation of delivery in VL01N

Dear All,
I have created a sales order in VA01 .Then while I am trying to create delivery in VL01N system is giving error no : BS051 Create delivery" not allowed (User Status PREP, object )
Please let me know what is missing in this procedure .
Abhijit Das

Dear Abhijit,
Have you assigned any Delivery-related Status Profile in your Sales Order?
Best Regards,
Amit

Creating Error message during creation of SC using create limit item option

Hi,
I am using option "create limit item" option to create a service SC, now i need to set an Error message if the value in the "value limit" field is lower than the value in the "expected value" field during the creation of sc and i should not be able to order such cart. Currently there is no message displayed and i can create a SC with the lower value in the value limit field.
Please suggest.
Regards
GGL

Hi. Try BBP_DOC_CHECK_BADI to issue a custom error.
Regards,
Dave.

Error during creation of datasource using BI publisher

Hi All,
I have installed BI publisher 10.1.3.4.2 from http://www.oracle.com/technetwork/middleware/bi-publisher/downloads/index.html for linux - 32/64.
I am able to see the reports under Reports tab in BI publisher. But need datasource to get actual data. During the creation of datasource, tried Driver -11, 10 and driver class oracle.jdbc.OracleDriver, oracle.jdbc.driver.OracleDriver but all the time error is coming -
[100512_022947829][][EXCEPTION] java.sql.SQLException: ORA-28040: No matching authentication protocol
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:277)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:243)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:304)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:430)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at oracle.apps.xdo.servlet.data.JDBCDataSource.testConnection(JDBCDataSource.java:268)
at oracle.apps.xdo.servlet.ui.admin.datasource.UpdateConnectionServlet.doConnectionTest(UpdateConnectionServlet.java:411)
at oracle.apps.xdo.servlet.ui.admin.datasource.UpdateConnectionServlet.doPost(UpdateConnectionServlet.java:151)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:100)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Not sure if I need to install or configure any other thing.
Please let me know how can I proceed?
Regards,
Sourabh
Edited by: 963380 on Oct 7, 2012 7:48 AM

The error is described here: http://oracledocs.shu.ac.uk/oracle/B28359_01/readmes.111/b28280/toc.htm#autoId36 , so talk to your DBA about setting the appropriate authentication protocol version.

How To Change The Patter generates during creation of Prog using SE38

Dear Guru,
I have Encountered an Issue.
The Scenario Is like this :-
As soon as we create a new prog using SE38 it automatically generates a standard pattern like below :
*& Report ZSR_TEST_05
REPORT ZSR_TEST_05.
But the requirment is like this as soon as we create a new prog using SE38 it automatically it should generate the The Pattern like below :--
*& Project            :
*& Program Name       :
*& Transaction Code   :
*& Program Type       :
*& Functional Domain :
*& Technical Coding   :
*& Functional Guidance:
*& Coding Review      :
*& Spec. Review       :
*& Program Description:
REPORT ZSR_TEST_05.
After going through sdn documentation i have identified that using dynamic pattern we can create this and call that dynamic pattern using PATTERN button in ABAP editor.
But the thing we require as soon as we generate the prog thr. SE38 atomatically all the details must generate before the report <report_name>.
For achieving thins what i have to do ... please show me some path to achieve this
Thanks & Regards
Saifur Rahaman

Hello Saifur
Not sure if you can make SE38 to do what you want (yet it is likely). If you do not want to create lots of ABAP patterns why not define a simple ZTEMPLATE report containing the basic set of comments:
*& Project            :
*& Program Name       :
*& Transaction Code   :
*& Program Type       :
*& Functional Domain :
*& Technical Coding   :
*& Functional Guidance:
*& Coding Review      :
*& Spec. Review       :
*& Program Description:
REPORT ZTEMPLATE.
*& Initialize report
INITIALIZATION.
*& PBO of Selection-Screen
AT SELECTION-SCREEN OUTPUT.
*& PAI of Selection-Screen
AT SELECTION-SCREEN.
*& Begin of Main Program
START-OF-SELECTION.
*& End of Main Program
END-OF-SELECTION.
New reports are then created by copying your ZTEMPLATE template.
Regards
Uwe

Disable certain fields during the creation of SC using "create limit item"

Hi,
I have a requirement to disable certain fields from the role "SHOP" associated with the operational purchaser role. I would like to disable the fields "Unlimited check box", "Service Agent", " Invoice Only radio button", "Unknown account assignment radio button" from the screen I get during creation of SC using the option "Create Limit Item". Also i need to disable the option "Good / Service" entry box as we are using only free text items and donu2019t want this option to be seen in the screen when using the operational purchaser role.
Please advise how can I achieve this.
Regards
GGL

Hi,
I have a same requirement to disable certain fields from the Shopping Cart Limit Item. I would like to disable the fields "Service Agent", "Unknown account assignment radio button" from the Detail screen. during creation of SC using the option Limit Item . Also i need to make default Value "Known" and "Invoice Only". But this is in SRM 7.0. Notes You have mentioned supports only Release 5.5, But I am in Release 7.0. Any idea?
I appreciate your help
Thanks,
Monica

Avoid outbound delivery split creation during GI

Hi guys,
Every time we perform a GI in /SCWM/PRDO for a partial picking, the system creates a delivery split, leaving the rest for the original delivery.
I want to avoid the delivery split! The operators have a procedure to check the warehouse tasks before the GI, but sometimes they forget to check and they post the GI with open quantity.
For this reason I would like to know; if there is a way to block the GI when there are items with open quantities?
Thank you all.
Anderson Ranéa

Hi
If you want to prevent outbound delivery split, you may refer to note 1600871 for details, it has 2 solution provided to avoid the spliting.
Hope it helps..
BR
Vic

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.

Item categories are re-determining based on batch split during delivery

Hello All,
During delivery item categories of bill of materilas are changing based on batch split.
Scenerio: item level bill of materials configured.
Ex: COMPUTER is main item and item category group is LUMP and item category is TAP
but it is relevent for billing as per client requirement
key board, cpu and moniter are bills of materilas item category group is NORM and item category is ZZTA
These above items are relevent for delivery and not relevent for billing
Problem: During batchsplit in delivery item category determining as "TAN" for item category ZZTA
That can be shown when we click on batch split button for sub line item (moniter, cpu) category ZZTA
all batch split line items are copied to billing and getting account determination pricng error because of TAN is relevent for billing
Could you suggest me to prevent the TAN item category for batch split in delivery
Should TAE item category to be maintained for delivery item categories
currently delivery item categories are configured as shown below
del doc type=zlf , item cat. group=lumf, higher level item cat.=tap, No default item catgory
Thanks & Regards

Hi
In the asign item cateogories use usage CHSP (Batch split) for norm and assign default item category as ZZTA. This will get determined your item category when you use batch split.
Spro --> Sales --> Sales document Item --> Assign item categories

Enhancement during creation of outbound delivery to update serial number

Dear ABAPers,
Is there any Enhancement during creation of outbound delivery to update the serial number.
My Requirement is In the VL10B transaction Outbound delivery will be created for the Purchase Order. During this time i want to update the serial number in the Outbound Delivery.
Any Replies.....
Thanks & Regards,
Ashok kumar.
Edited by: M Ashok kumar on Jul 22, 2010 6:41 AM

hi
check INVOICE_UPDATE
Thanks
Edited by: saurabhmani on Jul 22, 2010 3:00 PM

Delivery Split during creation of delivery using ME2O

Similar Messages

Maybe you are looking for