Embargo Block on Delivery Document due to future Delivery Date

Hi Experts,
I am facing a very strang problem where the Delievry Document for STO is getting embargo block. Some how its been figured out that the Delivery Date in the Delivery coming from STO is a future date of year 2011 and when you delete the Delivery and create a new one after changing the Delivery Date in STO from 2011 to a date under 12/01/2010, the system does not block it for Embargo.
Don't understand how date is linked to Embargo.
Please Help
Regards
DG

Hello DG,
check in transaction /SAPSLL/CNTRY (or via path /sapsll/menu_legal --> Legal control - Export --> "Embargo" Maintain Country-Specific settings) your conditions for Embargo checks. Check whether validity is maintained appropriately.
BR,
Gabriel.

Similar Messages

  • Delivery split due to Conflicting Header data (ABSSC:  uF0E0 000002)?

    Hi All,
    I have 2 line items of same material with different Schedule lines. I created a delivery for line item 1.Then I tried to enter the 2 line item in the delivery System is throwing error message as below :
    Item 10: Delivery split due to Conflicting Header data (ABSSC:  <  000002)?
    Item 20: Delivery split due to Conflicting Header data (ABSSC:  <  000002)?
    Can some body explain why this message is coming and how to resolve this?
    Regards,
    Ram

    HI,
    I have 2 line items of same material with different Schedule lines. I created a delivery for line item 1.Then I tried to enter the 2 line item in the delivery System is throwing error message as below
    Rather than  going one by one Go to VL10A & VL10C and generate the Background Delivery number and go to VL02N do the PGI
    or By using the T-Code VL01N give the Selection date is Future date like if one line item is today's Date and other line item is 25.08.2011 so you need to mention  Selection date 25.08.2011 and system will accept 2 line items before that check the Stock in MMBE & MB52
    The above solution is based on Single SO if it is multiple SO better to Go to VL10A or VL10C
    and also check the Configuration like if it is Different SO with Same customer ,you need to check the order combination in Customer master
    Revert
    Regards,
    Prasanna
    Edited by: prasanna_sap on Aug 23, 2011 11:09 AM

  • Delivery split due to conflicting header data

    hi experts,
    we have implemented CRM services with R/3 as back end system.
    when ever a service order in crm with more than one  material in line items get replicated to r/3 as sales  order .during delivery we are getting the following error.
    *Item 000020: delivery split due to conflicting header data (Function SH: Address Number: 9000001514 <-> 9000001509)*
    *Message no. VL033*
    even though the Ship to party is same.
    can any one of you hlep me to solve this problem
    Thanks & regards,
    SR

    Hi SR
    This could be because of the order combination field that has been marked in your customer master in R3. 
    The field KZAZU is nothing but the order comination information in table KNVV
    Hope this will help you...
    Regards
    Ramesh S. Narayanan

  • Multiple Delivery document for Single Inbound Delivery

    Dear Experts,
    My scenario is;
    I have 2 Purchase Orders.
    PO 1 -> 100 QTY
    PO 2 -> 150 QTY
    I have done partial GRN against PO 1. In confirmations tab the inbound delivery no is shown.
    Latter I want to do inbound delivery for the remaining qty of PO1 and PO2 in the same inbound delivery. But while trying to pull the POs delivery, 2 delivery document are generated. I need to do the inbound delivery in single delivery document.
    Kindly guide.
    Thanks & Regards
    Ranjit Simon John

    Can you clarify on that: error message "Please maintain Table T163L". I have maintained inbound delivery in confirmation tab.
    I just checked on table T100 but I cannot find such message, it could be that T163L is a variable which would make it a pretty generic message, but I would be interested in the message number.
    I have 2 message with T163 mention in the text which are:
    E
    VL
    664
    There is no entry for confirmation category & in T163D
    E
    VL
    665
    No delivery type assigned to confirmation category & (table T163D)
    Further you are saying you have already maintained an inbound delivery in the confirmation tab.
    Isn't this a kind of duplicate if you have already an IBD maintained and you want create another one?
    Looking at this message again, it starts for me to make sense then, because the customizing is about sequence , and you do not have an entry that you expect another IBD as a second activity in your confirmation sequence.

  • Item 000090 Delivery Split due to conflicting header data (FKAIV - IV)

    Hello,
    I am getting the above message. I would like to know where can I find the Inter Co Bill type (FKAIV) for the materials, so that I can see where it is different.
    P.S. I am an ABAPer.

    Hi
    It seems you are running Intercompany Process.Please check in the LIKP table(LIKP - FKAIV).There you can see the data.
    NOTE: Kindly search in the forum also
    Regards
    Srinath

  • Open Sales order, Delivery docuement, Billing document, Item

    Hi Gurus,
    Kindly help to view the following items for a particular customer.
    1) Open sales order value
    2) Open Delivery docuement value
    3) Open Billing document value
    4) Open item.
    I presume for viewing open sales order VA05N and to view Open item FBL5N would suffice. Please correct me if i am wrong and let me know about points 2 and 3.
    This is required because, my client is facing some figure mismatch while executing F.35 tcode. I am trying to analyze the differnce of figures while doing a Static and dynamic credit check.
    Thanking you in advance
    ficoguy.

    Dear ficoguy,
    1) Open sales order value
    Tcode: VA05 (select OPEN SALES ORDERS)
    optional method: SE11/ TABLE VBAK/ INPUT customer code as KUNNR, fetch the list.
    Input the VBELN in VBUK and filter with RFSTK='A'
    2) Open Delivery document value
    Tcode: VF04 (OUTPUT DATA FOR BATCH PROCESSING-->CHECK LIST DISPLAY)
    DOCUMENT TO BE SELECTED = DELIVERY RELATED
    optional method:(same as above except the FIRST TABLE)
    SE11/ TABLE LIKP/ INPUT customer code as KUNNR, fetch the list.
    Input the VBELN in VBUK and filter with RFSTK='A'
    3) Open Billing document value
    TCode: VF05
    Selection criteria : OPEN BILLING DOCUMENTS
    4) Open item.
    Tcode : FBL5N
    Check and revert back.
    Thanks & Regards,
    Hegal K Charles

  • Issue in Delivery document Status update

    Hi ,
    We are facing serious issue in delivery document delta extraction via Delivery item Datasource (2LIS_12_VCITM). This leads to incorrect Pending logistic figures in stock and dispatch report. Details for the issue are as follows.
    Datasource used : 2LIS_12_VCITM
    Issue Description :
    The goods movement status flag (WBSTA) field from the ECC table VBUP is not correctly extracted by the standard deliveries item datasource (2LIS_12_VCITM) during delta loads.
    Steps taken to rectify the issue
    -     We have removed the commit work statement and applied in parallel update task in ECC. Include : ZSD_INCL_DEL_SAVE_FINS
    -     Setup tables for Delivery were filled in ECC.
    -     Historic data was deleted from the Delivery cube in  BW
    -     Data was pulled into PSA (Info package u2013 Full Update)  from where it was loaded to DSO in overwrite mode  (Historic data was not deleted from DSO)
    -     Data from DSO to delivery cube was loaded with DTP setting as Full Update.
    -     After complete data was updated in Cube the DTP setting were changed to Delta.
    -     Delta info package was scheduled  for the capturing the document changes from next load.
    -     Goods Movement status for all the documents created till this point was exactly similar to the status in ECC.
    -     The goods movement status flag (WBSTA) field from the ECC table VBUP is not correctly extracted by the standard deliveries item datasource (2LIS_12_VCITM) during delta loads.
    Example              :
                                    Delivery document no:  2131260470 is pulled with goods movement status u201CAu201D in firstly load (here BW Delivery status matches
                                        With ECC )
                                   Before next delta load status in ECC (WBSTA) changes to u201CCu201D (PGI Complete) along with updated u201CGoods Issue Dateu201D
                                   Extractor fails to capture the change in document ,thus status in BW remains as u201CAu201D with no date updated in u201CGoods Issue Dateu201D
                                       field.
    Steps for Reconstruction :
    1)     Check the value of Goods movement status and actual goods issue date fields in the PSA for the datasource 
    2LIS_12_VCITM in BW for the sample delivery mentioned in the attached file
    2)     Compare these values with the ones in the ECC table VBUP.
    Kindly help at the earliest.
    Regards,

    Hi,
       Could anyone please reply as its quite critical.
    many thanks in advance,
    regards
    pramod.

  • Problem in finding Idoc number from Delivery document number(VERY URGENT)

    Hi experts,
    I have a delivery document number.Now i have to find the Idoc number for thet delivery document and extract some necessary data from one of the segment of that Idoc.So I am not able to find a link through tables .
    So I exact query is 'what is the selection method i have to follow to get the idoc number given the delivery document number'.
    Regards,
    Praveen.
    Edited by: Praveen Jada on Mar 14, 2008 12:15 PM

    That's what I meant, do the following query:
    DATA: LT_DOCNUM TYPE TABLE OF EDI_DOCNUM.
    SELECT DOCNUM
      INTO TABLE LT_DOCNUM
      FROM EDID4
      WHERE SEGNAM EQ 'E1EDL20'
      AND SDATA EQ '0001234567%'.
    This will list you all the IDOC numbers in which delivery number 0001234567 appear in the delivery header segment.
    Depending on your process it's probably going to be one entry only.
    Hope that clarifies it,
    Michael

  • Delivery document type settings

    Hi all,
    In standard SAP For LF delivery type, Default order type DL (Delivery with out sales order reference) is assigned.What is the use of this.
    For delivery with out reference to sales order system will not allow us to use delivery type LF.
    we only use Delivery type LO.Then why DL is assigned to this.
    One more question for LO delivery type DL is assigned.Can I see DL anywhere in the delivery document?
    Regards
    Mano

    Hello Mano,
    It is not the case that you cannot use LO for Delivery with Order reference or LF without Order Reference.
    It is because it has been set in the Delivery document parameter setting that it requires an Order Reference or not .
    You can change it if you want by making a copy of the Document type so that Standard is maintained.
    For your query,SAP has probably maintained most of the  Delivery documents with Default Order as DL.
    Because if you create a delivery with or without reference the items declared in the Delivery document should have some reference document before it.
    This is the F1 help which clearly states the use of declaring the Order type
    Default order type for deliveries without reference to order
    The default for a "pseudo" order type for deliveries or delivery items that do not refer to an existing order.
    Use
    When you create delivery documents that do not refer to existing orders, you must provide some of the control criteria that are normally copied from a sales document header into the delivery document.
    Example
    A delivery document, for example, needs information about which item types need to be defined.
    Procedure
    You can define a pseudo order type in Table TVAK. When you create a delivery that does not refer to an existing order, the system automatically uses the pseudo order type.
    Hope it is clear to you now.
    Regards,
    Karthik

  • Archiving  inbound delivery documents

    hi gurus,
    can you help in in archiving inbound delivery documents.
    This inbound delivery document is created after purchase order is created with confirmation control.
    Pls tell  me the programme through which i can do it.
    What should i do before doing the archiving.

    >  archiving inbound delivery documents.
    Hi Pavan,
    The following link will help you understand the concept of archiving as well the implementation process:
    [Data Archiving|http://help.sap.com/saphelp_nw04s/helpdata/en/2b/086f3b6c980c3be10000000a11402f/frameset.htm]
    Regards,
    Swapna

  • How to find the event time segment details from delivery document

    Hi,
    In the delivery document at header level in Dates tab i have maintained begining Plan date where Event = Shipment.
    But that field is in structure.
    How to fetch those(Begining Plant Date) details in to report,
    I have tried from Function module side also, i have not found any function module which is related to this field.
    If any body give some solution, that will be great help for me.
    Regards
    Lakshmikanth

    I have tried with those table(TSEGH & TSEGE), i have not found the begin plan date for that event. where event = shipment.
    We are using 4.7 version. Here we have found one function module: TSEG_DIALOG_DATA, but iam unable to find the input details.
    Here the input options are:
    IF_HANDLE
    IF_DIALOG_VIEW
    IF_DIALOG_ZONE
    May i know what are these inputs, what exactly i have to pass to this function module.

  • STO Partner Copy Control to Outbound Delivery Document (NL)

    Hi -
    Partner Schema CR for 0003 UB Type has been maintained in configuration, which allows CR (Freight Forwarder) partner function to be manually added to UB Document Types (Partner Determination Process u2013 0003 Stock Transfr PurOrd).
    However, even with this configuration the CR partner does not copy to the Outbound Delivery Document.
    After some analysis, I found the following:
    In program SAPLMEPO (MM06EF0P_PARTNERS) FORM PARTNERS in line 97 u201Ccheck EKKO-BSAKZ equal to spaceu201D; if purchase orders have EKKO-BSAKZ = 'T' then never determine partners. I have checked the EKKO table for field BSAKZ and all STOu2019s have a T in that field. If the code is looking for <blank> in order to apply the partner it looks like the program will not attempt to retrieve the Partner Functions with BSAKZ = T.
    All other partners are getting copied to the outbound Delivery, such as PI (Invoicing Party), DP (Delivering Plant), SH (Ship-To)etc.
    Is there a way to have Freight Forwarder partner copy control to Outbound Delivery document at time of Delivery create from either Vendor Master or Customer Master for STO (UB Purchase Order type) / Delivery type NL?
    Thank you,
    Karen

    remark: for me the check is in line 113 (SAPKH60407).
    Please read OSS note 842829:
    2. The system does not transfer the partner data from the STO to the replenishment delivery. This particularly applies to the forwarding agent. The replenishment delivery uses only the customer of the receiving plant (EKPO-WERKS) as a partner. In the replenishment delivery, this customer (EKPV-KUNNR) is the direct goods recipient. The customer is not the sold-to party or a general debtor, for whom the system would determine a (different) goods recipient using the customer master in the replenishment delivery. If the PO header contains a vendor, you can use a modification to transfer the vendor as a partner to the replenishment delivery, if required. However, this is not the standard system behavior. There is no known modification for transferring the forwarding agent.

  • Deriving Material Document No from Outbound Delivery Document No

    Hi,
    We have a requirement where based on the out bound delivery document number and the delivery line item number, we have to derive the correspponding material document number. Please suggest on how to go about this.
    Thanks and Regards,
    John

    Hi!
    Try this:
    select single matnr from lips into l_matnr
      where vbeln eq OUTBOUND_DELIVERY_NUMBER
          and posnr eq OUTBOUND_DELIVERY_ITEM
    Edited by: Petr.Plenkov on Jun 3, 2010 1:14 PM

  • 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

  • Sap standard report for delivery document block.

    Hi,
    We want to block delivery document for further processing that picking and PGI.
    For that we are looking for sap standard report if available so we could provide it to client.
    so we need
    SAP standard report for blocked delivery document.

    Hi,
    As far as my understanding there is no such report but you can try with report MATERIAL WHERE USED LIST
    Please find t-code for this as due to system unavailable i am not mentioning t-code for same
    kapil

Maybe you are looking for