Delivery creation select variants must be checked

Hi Gurus,
in selection variants for delivery creation by batch were wrong on 2 points :
date selection was too large (till D30 instead of D5)
shipping point was incorrect.
Please help me

Goto T.Code SE38 and give the program name. You will find 4 options below and choose the variant and click the Change Button.
You will be in the next screen, here you will have the option to change the variant, now click the change button and change the Shipping point.
Once done save and back to the previous screen. Now press the Attributes button, this will take you to the screen where they have defined the Selection variable. You will find a Selection variable button on top of your screen, press that and this will take you to the next screen here you will find that the date has been maintained as D30, change this to D5 and save the variant.
Lo! you are done. verify the date one more time before you run the job and that's it.
Regards,
Mani.

Similar Messages

Delivery Creation (Selection date on VL01N)

Hello Experts,
I am trying to create a delivery for an Order. Procedure followed is,
Goto T-code VA02. Enter order Number, press enter
Goto menu Sales order ==> Deliver. This calles the T-code VL01N.
My question is, I am expecting the requested delivery date from order to be copied to the selection date of T-code VL01N,
But I am not getting it, always the Current system date is copied to the selection date.
Please suggest me how to copy the requested delivery date to the selection date of t-code VL01N.
Cinfig/Programming?
Best Regards,
Mohammed.

Hi
Normally,system date gets copied as the "Selection date" in the Create Delivery(VL01N) screen by default which you can change.
You require that the "Requested Delivery date" to be copied as "Selection date" , but what is the purpose of it ? I think ,it will not be helpful to you.
You need to understand clearly what is "Requested Delivery date", "Confirm Delivery date" and "Selection date".
"Delivery date" or "Confirm delivery date" is the date on which Customer acknowledges the receipt of goods/Delivery.
"Requested Delivery date" is the date on which Customer wish to receive the goods/Delivery.
It is a Customer's wish ,which we may or may not be able to meet keeping different lead times in consideration.
System does "BACKWARD SCHEDULING" first to check whether the Cutomer's Requested Delivery date can be kept or not (for this you have to understand Delivery scheduling in details which is easy).
If it finds that the "Requested Delivery date" can be kept then it confirms the "Requested Delivery date" as "Confirm delivery date". Here "Requested Delivery date" and "Confirl Delivery date" are same.
If it finds that Requseted Delivery date is not possible to confirm then it goes for "Forward scheduling" and gives a new "Confirm Delivery date". Here "Requested Delivery date" and "Confirm Delivery date" are different.
Now, coming to "Selection date".
Selection date is the date on which Shipping processing begins. It is either the "Material availability date" or the "Transportation Planning date" , whichever is earlier.
That means, Shipping process starts on the "Selection date" and goods reaches the Customer on the "Confirm delivery date".
So, in the "Create delivery" screen (VL01N), in the "Selection date" you need to enter the "Material Availability date" or "Transportation planning date" whichever is earlier (you can enter a later date also but not before date)and you can get those date from the schedule line of the item.
Item details > Schedule line > click on the "Shipping " tab/button below.
Suppose "Material av date " is 20/03/2009 and "Tr palnning date" is on 21/03/2009 in the schedule line then you need to put "Selection date" as 20/03/2009(as it is earlier between the two dates) or some later date also.
Therefore, copying the "Requested Delivery date" as "Selection date" will not be very useful for your Sales process as in the "Selection date" either you should enter the" Material av date" or "Tr planning date" whichever is earlier.
But, if still you require it to happen , then you have to take your ABAPer help.

Confirmation control key check for inbound delivery creation

Hi,
Currently, in the Client's company, the process of receiving goods from purchase orders looks like that (SAP-wise):
- create a purchase order,
- receive goods using MIGO and automatically create an inbound delivery,
- pack the delivery and post goods receipt.
Recently, some patches have been installed, including one described by note 1602047 (which basically enforces checking confirmation control keys if goods receipt assignment and goods receipt relevance are activated for inbound deliveries). Note says that it only affects two-step stock transfer and creation of automatic inbound deliveries using SPED output but it seems it also affects other basic processes like PO receipt in MIGO.
Now, when using the old control key (that had MRP-Relevant and GR-Relevant fields checked), the system is unable to automatically create an inbound delivery after the goods receipt is posted with MIGO (with message VL148 - Not possible to create an inbound delivery). I learned that this is because the "GR Assignment" field must be checked in the confirmation control key so it's possible to automatically create aninbound delivery after receiving a purchase order in MIGO.
After changing the confirmation control key to have the missing field checked it's not possible anymore to receive goods from PO in MIGO as the PO requires shipping notification in order to be processed in MIGO thus requiring of manual creation of an inbound delivery.
Is there any way to skip this check so the process would remain the same (this model has been working fine for few years in the Client's system) and the inbound delievery would be created automatically after posting the receipt in MIGO?
Thanks in advance,
Piotr

Hi,
don't know if you found a solution, but we received the following message from SAP:
The advent of the new version requires some attention to the users. It
was necessary to avoid inconsistencies which in the past version the
system was susceptible.
Main Program SAPMM07M
Source code of MM07MLVS
sy-msgid VL sy-msgty E sy-msgno 148
I have checked the process and through debugged I could confirm the
following information SAP is providing to all similar incidents reportedfor us:
Error message VL 148 is issued if in the confirmation control key used
in the purchase order, the fields for MRP-relevance (T163G-KZDIS),
GR relevance (T163G-WEREL) and GR assignment indicator (T163G-WEZUO)
are not set.
The correction of note 1602047 was necessary to avoid inconsistencies
(table EKES) in the purchase order. Without having the GR assignment
(T163G-WEZUO) set, there is no unique reference created between the
purchase order history (table EKBE) and the inbound delivery
confirmation (table EKES) at goods receipt which leads to a problem if
several inbound deliveries exist for the same purchase order.
If you set T163G-WEZUO to 'X', this assures that, for an inbound
delivery, the confirmation record (EKES) belonging to this inbound
delivery (EKES-VBELN) is also accurately updated at goods receipt.
How to solve the issue?
Use a confirmation control key with the GR assignment indicator set
and then create the inbound delivery with VL31N. If you want to be able
to create the inbound delivery with reference to a certain line item in
the PO, use transaction VL34.
If you still want to use transaction MIGO, there is the following
workaround:
- Create a purchase order without any confirmation control key
- Create a goods receipt (GR) in transaction MIGO with reference to this PO and post the GR to a non-HU-managed storage location
- Create a transfer posting with MIGO using movement type 311 to
transfer the goods from the non-HU-managed storage location to the
HU-managed storage location.
As the transfer posting is an additional step for the user, the whole
process could be automated using a partner storage location
(T001l-PARLG) for the GR which then triggers (through a modification)
the BAPI 'BAPI_GOODSMVT_CREATE' to create the transfer posting without
user interaction.
I hope to have satisfied you on the reason why it is now happening and
also I believe you can explain to business that it is a new behavior
necessary done from SAP side to avoid worse situations, we are aware of
potential dissatisfaction it might cause. SAP Support is always
available to clarify any issue.
Sorry for not having a more positive answer.
I hope it helps!
Leentje

Dynamic creation of date in selection variant

Hi All,
I have a Z program for updating a field in BOM item. One of the input field in the report is "Valid From Date". Actually the current date is automatically fetched through a function module and it is defaulted in that field.
Our client is using selection variant for ease of use. The problem here is old date in the selection variant is replacing the current date. I want current date to be created automatically during insertion of variant also. How can i solve this problem. Is there any selection variable inside the variant for dynamic creation of Date?
Thanks
Sankar

As I know there is no setting for this. For any std or Z report variant function with L should act same way...anyway you discuss with your ADABer.
See the help for variables
Selection Variables
The following three types of selection variables are currently
    supported:
o   Table variables from TVARV
        You should use these variables if you want to store static
        information. TVARV variables are proposed by default.
o   Dynamic date calculations:
        To use these variables, the corresponding selection field must have
        type 'D' (date). If the system has to convert from type T to type D
        when you select the selection variables, the VARIABLE NAME field is
        no longer ready for input. Instead, you can only set values using
        the input help.
        The system currently supports the following dynamic date
        calculations:
        Today's date
       From beginning of the month to today
       Today's date +/- x days
       First quarter ????
       Second quarter ????
       Third quarter ????
       Fourth quarter ????
       Today's date - xxx, today's date + yyy
       Previous month
o   User-specific variables
       Prerequisite: The selection field must have been defined in the
       program using the MEMORY ID pid addition. User-specific values,
       which can be created either from the selection screen or from the
       user maintenance transaction, are placed in the corresponding
       selection fields when the user runs the program.
The SELECTION OPTIONS button is only supported for date variables that
   fill select-options fields with single values.
i.e means we can do that with D also.

Serial Number validation during Delivery Creation itself(PGI-system checks)

Process:
Sales Order PR(Purchase Order) GR( New Serial Numbers are created automatically or manually keyed in)
Once the Goods Receipt is received, we do the (SO) DELIVERYu2014SERIAL NUMBER ASSIGNMENT Post Goods Issue
Issue:
Current Serial Number Profile Management does not do a valid serial number check during DELIVERY CREATION where we do a SERIAL NUMBER ASSIGNMENT.
Only during POST GOODS ISSUE, the check happens for valid serial numbers; this is too late in the game for business as there is a time lag of 3 days from the DELIVERY CREATION and PGI.
Reason being--- We donu2019t check the following u201C Existing Stock Checku201D( which does a serial number validation during delivery creation as well)
SPRO>Plant Maintenance and Customer Service>Master Data in Plant Maintenance and Customer Service>Technical Objects>Serial Number Management>Define Serial Number Profiles
If we check this option, the business requirement to do a valid serial number check does happen during delivery creation, however we cannot create new serial numbers during Purchase Order- GOODS RECEIPT.
QUESTION:
Can we have the system check the valid serial numbers from stock during delivery creation and serial number assignment.
And Also create new serial numbers during Purchase Order- Goods Receipt.

Hi
1.In std SAP its not possible to check the serail number during Delivery creation, through enhancement it can be done.
2.During GR for PO serial numbers can be created.
Rgds
Ramesh

Hard Check During Delivery Creation

Hello Experts,
Need your advice. I am stuck up in a enhancement issue during delivery creation. i am working for passenger vehicle company.
Back ground Info.
the company procures chassis from vendor & builds bus body over it. there are various types of chassis & each is uniquely identified in SAP by Material No. & also mentioned in BOM created for bus. when chassis is received , equipment is created using T-code IE01. After this one more equipment is created for bus which is called BBD Serial No. The equipment for BBD serial no holds chassis serial no. My issue is at the time of creation of delivery using T-code VL01N the user puts the BBD Serial No manually in a dialog box provided, This BBD Serial No is not capturing in the importing structure IT_XLIPS of BADI "LE_SHP_DELIVERY_PROC" Method "Delivery_Final_Check".
I have to put a check during delivery creation for consumption of Chassis , if the Chassis is consumed during production phase a Mat Doc will be generated with movement Type 261. As such we don't knew the Mat Doc for Chassis Serial no Consumed during prod phase. so to derive chassis no in the BADI against which we have to check for it's consumption. The user provide BBD Serial no in a standard dialog box in VL01N.
Can we use Field Exit for this or any other BADI Should work.
Best Regards
Priyesh Shah

Hi Priyesh,
Below steps may help you to get the value of the standard dialog box provided in the screen.
1. Find the field name of the standard dialog box provided in the the screen for BBD Serial no.
2. Implement below code in the BAdI "LE_SHP_DELIVERY_PROC" method.
FIELD-SYMBOLS: <fs> TYPE BBDFIELDTYPE.
ASSIGN ('(SAPMV50A)BBDFIELDNAME') TO <fs>.
Now the field symbol <fs> will hold the value passed in the dialog box.
Please try and let me know if it is working or not.
Thanks
Gangadhar

Check amount of transition stock during inbound delivery creation

I want to move stock between plans, therefore I have the following steps:
1. Stock Transfer Order (STO), e.g. 500 pieces
2. Sending plant: MIGO (GI for STO) with MT 351 to post to transition stock, e.g. 100 pieces
3. Receiving plant: Inbound Delivery with reference to STO VL31N
4. process Inbound delivery in warehouse (SAP-WM)
The question is:
During step 3, when accessing VL31N the system proposes the full order quantity (e.g. 500 pc.)
I can change the amount to any amount I like, e.g 240 pieces.
How can I tell SAP, that Inbound delivery creation is only possible for the amount
which has been posted to stock in transition (100 pieces)
I want an error/warning message in case user wants to create Inbound delivery quantity higher than the amount that has been posted to transition stock.
Any ideas?

MIGO in sending Plant?
How it is possible? MIGO means, Goods receipt. This should be in Receiving plant.
Sending plant should do the PGI
MIRO in receiving plant
Billing in sending plant
Payment from Receiving palnt and clearing in sending plant
Correct me if i am wrong
Thanks

Problem related to Outbound Delivery creation via Background Job

Hi ,
We are using the program RVV50R10C for creating OBD incase of STO .
Z variant is created to take care of selection parameters which inlcudes Shipping Point , Delivery creation date , Calc Rule, Delivery priority and shipping conditions.
The job is scheduled to run for every 10 minutes .
As planned the job is running for every 10 minutes but the OBD are created after 1 hour .
What are possible causes of this error.?
Please note that there exists enough stock.
Regards
Ramesh Ch

I think you will have the same problem when doing it manually with VL10B.
The creation is based on entries in an index. there is a userexit where you can influence how and when an entry goes into the index. E.g. you can speed up the overall performance if you do not update the index all the time, instead you are doing this with a background job from time to time.
Check if this is the case in your system.
this note may give you some hints:
Note 356061 - Incorrect index compilation caused by own checks

Prevent Outbound delivery creation in sales orders with delivery block

Hi gurus
We are facing the following issue:
Some sales orders have delivery block header and once they are saved an outbound delivery document is created; we want SAP system creates outbound deliveries only in those cases were sales orders have not a delivery block in header, is there any option or configuration we can use in order to prevent the creation of these documents?
Regards,
Edgar.

Well Edgar,
let's see then in spro
Logistics Execution->Shipping->Deliveries->Define Reasons for Blocking in Shipping
Check out the configuration of your delivery block reason and pay special attention to this instruction:
"In sales documents, you can either enter delivery blocks manually at header level (business data in the sales document header) or they can be proposed automatically by the system. In the latter case, the delivery block must be entered in the respective sales document type (see chapter
"Define sales document types"). In addition, the delivery block in the sales document header is only effective if the delivery block has been assigned to the respective delivery type."
It must be something in the configuration of the delivery block reason you're using.
Regards,
Edgar

Inbound delivery Creation(ASN) Process

Hi All,
Plz give end to end Process for creation Inbound delivery(ASN) No.
why should we take conformation control key in PO and not shipment notification tab there
thanks,
sunil sahoo

Config:
go to SPRO-MM-purchasing-Confirmation-setup confirmation control
here select the 10 and check the check box Create inb delivery
then select the line and click on the confirmation seq and make GR relevant, MRP relevant and GR assign (all three box checked)
Process Flow: -
1. ME21N - In PO, Confirmation Tab, select the confirmation control key as "Shipping Notification" or "Inbound Delivery"
2. VL31N - Create Inbound Delivery w.r.t. PO
3. MIGO - Goods Receipt > Inbound Delivery
If you dont select the conformation control key in the PO than system wont allow you to create the Inbound delivery agianst thePO.

Restrict Sales Order for Delivery Creation

Dear Experts,
We are supplying material to our customer (He is our subsidiary company). All the material codes within the two companies (i.e., our customer and us) are same. My customer is creating Purchase Order on us and through BDC program auto sales order is getting generated at our company. Pricing conditions are also copied from the PO to SO. We are not maintaining any pricing conditions for this customer.
My customer wants to supply the materials only against the sales orders created during the month only. Example: If auto sales orders are created during August'09 till 31st Aug, delivery should be created before 31st August only. From 1st Sept'09 onwards delivery should not create against the open sales orders created till 31st aug'09. When we try to do the delivery, system should not allow for creation of delivery from 1st Sept'09 onwards.
Can u please guide me whether we have any standard process for this to control the delivery creation? or we need to go for any development?
Your early reply in this regard is highly appreciated.
Thanks
Murthy SD

hi you can use scheduling aggrement concept for the same.
Alternatively , you can write logic in the exits .
program:
MV50AFZ1
code:
loop at xlips.
          select single vbegdat venddat from VEDA into (VEDA-VBEGDAT,VEDA-VENDDAT)
                                               where vbeln = xlips-vgbel
                                                 and vposn = xlips-vgpos.
             if sy-subrc = 0.
             if VEDA-VBEGDAT is initial and VEDA-VENDDAT is initial.
             else.
              if sy-datum ge VEDA-VBEGDAT and sy-datum le VEDA-VENDDAT.
              else.
              MESSAGE 'sales order referred is outside validity range' type 'E'.
              endif.
             endif.
             endif.
          endloop.
the code is to be writeen in exit of delivery i.e whenever delivery is being created wr to order it checks the dates in order
Rwd points if helpful
regards
chandresh

Mass Creation of Variants

I have hundreds of products that all have the same variant configurations, and I understandably don't want to pay someone to manually go through the WebTools interface to create all the variants. After looking through the WebTools database, I am planning on creating a little SQL script that will copy the variant information from one product to another.
1) Select all records from Variant table where ConfigPartNo = 'itemtocopyfrom'
2) Create new rows in Variant table that match the previously selected rows, switching out the ConfigPartNo to 'itemtocopyto'
3) For each of the first selected VariantIDs in the Variant table, Select all the records in the PartsVariant table where VariantID = VariantID
4) Duplicate each of those rows, substituting the new VariantID of the parts created in step 2
I can't find anyplace else that is affected by the creation of variants. Will this work, or is there a better way to approach this?
Thanks,
Derek

In case anybody else is interested, I whipped up this in Access VBA today. Basically all the form does is have two list boxes filled with all the products in WebTools. You can only select one from the FROM listbox, but you can select as many products in the TO listbox as you want. This code then loops through all of the selected TO products, duplicating all the variants settings of the FROM column.
My code is only lightly commented and does very little error checking, but it does the job. One thing to note if you end up using this code is that it doesn't check to see if it is duplicating variants, so if you click it twice or run it on a product that already has variants, it will add all of the variants from the FROM product.
Depending on how much I need to use this, I may extend it a little more so that I can choose to copy only certain variant categories rather than all variant categories, but we'll see. If I do anything significant, I'll hopefully remember to come post it here.
If anyone is interested in the original Access database that runs this, just send me an email at derek AT seatability DOT com and I'll send it over to you.
Dim SQL As String
Dim con As ADODB.Connection
Dim rsVariantFrom As ADODB.Recordset
Dim rsVariantTo As ADODB.Recordset
Dim rsPartsVariantFrom As ADODB.Recordset
Dim rsPartsVariantTo As ADODB.Recordset
Dim rsAutoVariantID As ADODB.Recordset
Dim rsPartsMaster As ADODB.Recordset
Dim CopyFromProductID As String
Dim CopyToProductID As String
Dim AutoVariantID As Integer
Dim varItm As Variant
    CopyFromProductID = lstCopyFromPartNo.Value
    'Open Database Connection
    Set con = New ADODB.Connection
    con.ConnectionString = "Driver={SQL Server};" & _
               "Server=server;" & _
               "Database=database;" & _
               "Trusted_Connection=yes"
    con.Open
    For Each varItm In lstCopyToPartNo.ItemsSelected
        CopyToProductID = lstCopyToPartNo.ItemData(varItm)
        Set rsVariantFrom = New ADODB.Recordset
        SQL = "SELECT * FROM Variant WHERE ConfigPartNo = '" & CopyFromProductID & "'"
        rsVariantFrom.Open SQL, con, adOpenForwardOnly, adLockReadOnly
        Set rsVariantTo = New ADODB.Recordset
        SQL = "SELECT * FROM Variant WHERE ConfigPartNo = '0'"
        rsVariantTo.Open SQL, con, adOpenDynamic, adLockOptimistic
        Do Until rsVariantFrom.EOF
            ' Copy all the old Variant Fields, only changing the ConfigPartNo to the new ProductID
            rsVariantTo.AddNew
                rsVariantTo.Fields("ConfigPartNo").Value = CopyToProductID
                rsVariantTo.Fields("Description").Value = rsVariantFrom.Fields("Description").Value
                rsVariantTo.Fields("ImageURL").Value = rsVariantFrom.Fields("ImageURL").Value
                rsVariantTo.Fields("MarketingText").Value = rsVariantFrom.Fields("MarketingText").Value
                rsVariantTo.Fields("VariantType").Value = rsVariantFrom.Fields("VariantType").Value
                rsVariantTo.Fields("DefaultPartNo").Value = rsVariantFrom.Fields("DefaultPartNo").Value
                rsVariantTo.Fields("RequiredFlag").Value = rsVariantFrom.Fields("RequiredFlag").Value
                rsVariantTo.Fields("SortOrder").Value = rsVariantFrom.Fields("SortOrder").Value
                rsVariantTo.Fields("SynchFlag").Value = rsVariantFrom.Fields("SynchFlag").Value
                rsVariantTo.Fields("SynchDate").Value = rsVariantFrom.Fields("SynchDate").Value
            rsVariantTo.Update
            ' Retrieve most recent Autoincrement / Identity value from connection
            Set rsAutoVariantID = New ADODB.Recordset
            SQL = "SELECT IDENT_CURRENT('Variant')"
            rsAutoVariantID.CursorLocation = adUseServer
            rsAutoVariantID.Open SQL, con, adOpenForwardOnly, adLockReadOnly, adCmdText
            AutoVariantID = rsAutoVariantID.Fields(0).Value
            rsAutoVariantID.Close
            Set rsAutoVariantID = Nothing
            Set rsPartsVariantFrom = New ADODB.Recordset
            SQL = "SELECT * FROM PartsVariant WHERE VariantID = '" & rsVariantFrom.Fields("VariantID").Value & "'"
            rsPartsVariantFrom.Open SQL, con, adOpenForwardOnly, adLockReadOnly
            'Return an empty recordset to add the copied PartsVariant rows
            Set rsPartsVariantTo = New ADODB.Recordset
            SQL = "SELECT * FROM PartsVariant WHERE VariantID = '0'"
            rsPartsVariantTo.Open SQL, con, adOpenDynamic, adLockOptimistic
            ' Copy all the old PartsVariant fields, only changing the VariantID to the new VariantID
            Do Until rsPartsVariantFrom.EOF
                rsPartsVariantTo.AddNew
                   rsPartsVariantTo.Fields("VariantID").Value = AutoVariantID
                   rsPartsVariantTo.Fields("PartNo").Value = rsPartsVariantFrom.Fields("PartNo").Value
                   rsPartsVariantTo.Fields("DisplayText").Value = rsPartsVariantFrom.Fields("DisplayText").Value
                   rsPartsVariantTo.Fields("UseBaseFlag").Value = rsPartsVariantFrom.Fields("UseBaseFlag").Value
                   rsPartsVariantTo.Fields("BaseAdj").Value = rsPartsVariantFrom.Fields("BaseAdj").Value
                   rsPartsVariantTo.Fields("SortOrder").Value = rsPartsVariantFrom.Fields("SortOrder").Value
                   rsPartsVariantTo.Fields("SynchFlag").Value = rsPartsVariantFrom.Fields("SynchFlag").Value
                   rsPartsVariantTo.Fields("SynchDate").Value = rsPartsVariantFrom.Fields("SynchDate").Value
                rsPartsVariantTo.Update
                rsPartsVariantFrom.MoveNext
            Loop
            ' Close PartsVariant recordsets and destroy object
            rsPartsVariantFrom.Close
            rsPartsVariantTo.Close
            Set rsPartsVariantFrom = Nothing
            Set rsPartsVariantTo = Nothing
            rsVariantFrom.MoveNext
        Loop
        ' Set the master record of the item to be a Variant Master
        Set rsPartsMaster = New ADODB.Recordset
        SQL = "UPDATE PartsMaster " & _
                "SET VariantMasterFlag = 'Y' " & _
                "WHERE PartNo = '" & CopyToProductID & "'"
        rsPartsMaster.Open SQL, con
        ' Close Variant recordsets and destroy object
        rsVariantFrom.Close
        rsVariantTo.Close
        Set rsVariantFrom = Nothing
        Set rsVariantTo = Nothing
        Set rsPartsMaster = Nothing
    Next varItm
    con.Close
    Set con = Nothing

Blocking a particular customer for immediate delivery creation

Hi All,
I have the following requirement
Right now whenever the sales orders comes from the customers through EDI, the deliveries were created immediately. This was set up through the sales document. This is being used for the document KE.
Now we need to stop this immediate delivery creation for a particular customer when orders come through EDI.
We can not do this by blocking the customer for deliveries(VD05) because this will block all the sales documents for deliveries. We need this to happen only for KE.
We cannot remove the immediate delivery creation set up from the sales document(KE) because this will affect all the customers(for other customers this should create immediate delivery).
I feel this has to be controlled through a user exit.
In that case what should be the logic used?
What should be checked before blocking the delivery for a particular customer?
Please advise on this.
Thanks in advance for your help.

Harini,
I am sure you do not want to take the route of achieving this by u2018Userexitu2019
Here is the alternate solution by simple customizing.
You need to do it in two steps:
Step 1: Define reasons for Blocking the delivery
IMG > Logistics Execution > Shipping > Deliveries > Define Reasons for Blocking in Shipping
Select : Deliveries: Blocking Reasons/Criteria
u2022 Define a blocking reason : say ZZ u2013 delivery Hold.
u2022 Check the Order check box
u2022 Save
Select: Delivery Blocks
u2022 Assign SO to Delivery ( I guess KE to whatever delivery type you have configured)
STEP 2:
Go to Customer Master record for whom you want to block them for normal process:
XD02 > enter customer master in change mode.
Select u2018Extrasu2019 tab in main menu
You see u201C sales and Distribution blocksu201D
Under this click on delivery block ( for All sales areas or desired sales area)
You will find the reason for blocking (ZZ) you created in STEP 1
Assignu2019 ZZu2019 to this customer and save.
Thatu2019s itu2026u2026 !!!!!
When a sales order received with this customer through your EDI, the order will be blocked for delivery.
One need to release the order manually by releasing this block
VA02 > sales tab : remove the block from the delivery block
Hope this helps.

Selection variant - authorization

Hi,
I'm using standard selection variants for internal orders and cost centers (created via KOK3, KS13, OKOV etc.).
Some of the variants are used in customizing (as receivers of assesment) so only some users should be allowed to modify such selection variants.
However there's NO authority check during creation or modification af a variant.
Does anybody know how to add an authorization check here? Modification with customer authorization object for instance.
Best regards,
Jacek

Hi,
Please try authorisation object S_PROGRAM for program SAPLSVAR.
Thanks,
Szymon

User exit for delivery creation in VL10B/VL10G-

Hi,
Is there any exits available for restricting the document type while the deliveries are selected/processed using VL10B/VL10G - delivery creation in background.
Scenario is when deliveries are created for STO's,the delivery is to be created for a selected document types(EKKO - BSART).Other types of document types have to be ignored when the delivery is created in background.
Regards
Deepak

Hello Deepak
You handle this through configuration while setting up Stock Transport Orders in MM.
Path: IMG/Materials Management/Purchasing/Purchase Order/Set up Stock Transport Order/Assign Delivery Type and Checking Rule
Here you a Delivery type for a combination of Plant and PO type. So those PO types which you don't want to be included for delivery creation will not figure in this assignment. I don't think you should go down the user exit route.
If you still need to explore user exits, look at OSS note 198137 for a list and purpose of VL10X based exits.
Hope this helps.

Delivery creation select variants must be checked

Similar Messages

Maybe you are looking for