BOL Output

I have a scenario where there are multiple deliveries in a Shipment for different Ship-to-parties. I need to send BOL using Fax or e-mail to only some Ship-to-parties on the Shipment. I created Output Type with new Condition table with fields Transportation Planning Point, Shipment Type and Ship-to-party, new access sequence, new output type. I created the Condition Records by giving the Ship-to-party and entering Partner Functions. But when I look at the Determination analysis, I get the message "524 Access not made (initialized field)". The Output type is not picking the Ship-to-party.
Any ideas on how to resolve this issue...

Hi,
If you are triggering the BOL output from the Shipment Header, then the pre-requisite is that all the Deliveries assigned in the Shipment must have the same Ship to party.
Since in  your case, it can have multiple ship to parties , you cannot trigger the BOL at Shipment Header based on the ship to party.
Rather , I would suggest an option.
Trigger the BOL output from the Delivery. based on the condition in the Shipment.
i.e., you can create an activity profile and there you can assgin the BOL output in the Delivery Section. and assgin this profile to a activity. like Planning, Shipment Start like that.
so that once the activity is marked on, the coresponding output is triggered in the delivery document.
if you maintain the condition record, then the output is triggered for only those deliveries.
regarding the form lay out. we can design in such a way that it looks the way we wanted it to.. since it can be more customized.
Hope this helps.
Thanks
Srini

Similar Messages

  • Print Freight terms on BOL

    Hi,
    can anyone please help me with this?
    How can we print freight terms : Prepaid or Collect or Bill to party on Bill of lading? I am print BOL in VT70.
    Thanks,
    Ratna

    I don't have any R/3 config steps. But i bet an ABAPER with the SAP SCRIPT/FORM used for BOL output type can definitely do the magic.
    We have our Buddy who did the same & it looks good in BOL.
    If somebody has Standard way, i would be happy to know the same.
    Thanks

  • BOL Determination

    Hi,
    In shipment, I am facing problem with BOL output type
    When I select forwarding agent as ABC and complete my shipment, I get two output type determined, as ASN - EDI and ZBOL
    But when I select forwarding agent as XYZ and complete shipment, I get only ASN-EDI output determined.  Why the system is not determining ZBOL output type for fowarding agent XYZ.
    ZBOL has a condition record for shipment type TL.
    Any clues!!
    Thanks in advance
    Deejay

    Hey Srini, thanks for your reply.
    We have not assigned any partner function to BOl, it is assigned to shipment type.
    So whenever we create shipment type TL, BOL should automatically gets triggered.
    Further, as I mentioned earlier, it is working for ABC forwarding aget.  In shipment, when I select forwarding agent as ABC, I get two output types determined ZASN and BOL.
    But for the same shipment if I select forwarding agent as xyz, I get only one output type determined.  ZASN.  BOL is not working for XYZ  Fwd agent.
    Thanks,
    Deejay.

  • Intermittent issues with SAP printing

    Hi ALl, We have been having intermittent issues with printing (more specifically BOL printing) on both ECC production  & Watre house production server recently. These issues occur at random hours and resolve themselves before the teams have had an opportunity to troubleshoot in detail. Also, both the Basis and hosting teams have analyzed the logs but haven’t reached a definite conclusion. Procedure used in printing: An outbound queue is created and processed in Warehouse Production and passed to ECC PRoduction. In ECC PRod an inbound queue is processed to update and trigger the shipment document. When the shipment document is completed it then triggers the print of the BOL output from the shipment. Then and only then is anything sent to the print queue.  AND it will be with user id = ALEREMOTE. The other printing works fine. Any thought..will be highly obliged.. Regards, VIcky

    Doug,
    If you have a service contract feel free to call in to the support line and you'll be able to work with someone on the phone. That'll be the quickest way to resolution.
    Feel free to send me a PM if you wish and I can take a look at the code and test it on our machine. 
    Notes for Branch AE:
    Please reply to This Post within 24 hours
    The US AE is expected to reply to all of your posts within 24 hours. Having this expectation will keep the escalation moving quickly and toward a fast resolution.
    You can also use other communication channels: Phone, Sametime, Lync,etc. to discuss the issue with the US AE. This can help with troubleshooting and quick diagnosis of the issue.
    Click here to provide kudos for a post on this page

  • Printing multiple copies of 3 page BOL in Duplex mode-

    Hi Gurus!
    I have created a smartform to print the BOL on front side and terms and conditions on back side. I used the duplex mode to print and it works perfectly fine. When I have a BOL with 3 pages of information , it prints the items on the front side and terms and conditions on the second side and it does everything absolutely correctly.
    At our organization we always print 5 copies of any BOL and that is when the problem arises. When we do a printing of the BOL form with number of copies set to 5 , it prints very akwardly with the settings. First it prints page 1 front and same thing on the back, then  again the first page on the first and its back and then front on the third side , then similarly 5 sides of terms and conditions and then followed by 5 sides of page 2 items and followed by 5 sides of terms and conditions, which is very akward. Actually it should print first set with page 1 and TC on back of it , then Page 2 and TC on its back and page 3 and TC on its side like it does when I make a single copy.
    Is there any settings that I am missing thats making the above happen when I print multiple copies of the BOL?
    Please suggest.

    Hi!
    Thanks for the reply. I changed the settings of the printer to 'Pass Copies as Separate Output Request(in SAP System)' and re-tried printing 5 copies of the BOL and it again seems to print the first page 5 sides then Terms and conditions on 5 sides, then again 5 sides of page 2 and followed by 5 sides of T&C.
    My settings on the smartforms is front page "D' and the back and the Last page is blank setting. This runs well when I just have to print one copy of my BOL , it prints the front page and then T&C on its back side , then again the second page and T&C on its back . This only messes when its more than one copy of the set of BOL.
    Please suggest as to what to do next to make it print in proper sets.
    Thanks and Regards
    Aarav

  • Multiple output types issue

    Hello,
    I configured two output types (Bill of lading & Packing list) for the application V7-transaportation. I am able to get both the outputs. Now, I am able to get a print for BOL and also a print preview. For Packing list I am able to see the screen view(print preview), but when I try to print it directly it gives me an error " output could not be issued" . When I go to Output-> screen it is showing me the output.
    I have maintained all the required print parameters and assigned the print profiles to the output types.Is there a problem with my configuration? can't I print two output types simultaneously?

    Hi,
    Is there a printer defaulted to your output types?  You can issue multiple outputs at the same time.
    If the output types have been determined in your document, then nothing wrong with the determination process.
    If the output can be previewed, nothing wrong with the SAPScript or Smartform.
    So maybe something to do with compatibility with the printer chosen.
    Phyllis.

  • Output not triggered during SAVE from Shipment

    Hi,
    We have a custom Idoc triggering from the Shipment. The output shows up in the output screen (as yellow) and it is set to trigger 'immediate - 4'. But when I save, it does not issue an output. No errors, nothing just does not trigger at all. If I go into the shipment again in change mode and then save it, then it triggers the output.
    The output is an custom idoc, transmission medium 6, attached program RSNASTED and the form routine is EDI_PROCESSING.
    I tried debugging the program (in update debug mode)...found that an internal variable XNAST-UPDAT is set to 'D' (a GERMAN comment in code says "no longer found or changed key"). The only key change I can think of is the shipment number initially with $0001 and then changes to the actual shipment #. But this should happen even for other outputs..for eg, BoL printout. It does trigger without a problem and for this this indicator is not set to 'D'.
    Any thoughts ?
    Regards,
    Anand

    Hi Anand,
    Have u resolved this issue... bcoz i m facing the same issue..
    Can u plz tell me how u resolved it..
    Regards,
    Siva Kumar S.

  • Global,intilization,input ,output parametrs to be assigned

    hi guys these is layout of my form to be added to existing smart form and fields to be added are below ,now can what should be added in global,intilization,input ,output parameters to be and in the  interface section and how should i create layout
    1     Whs BOL     VBAK-VBELN     Field is mapped from order header
    2     Order No     VBAK-VBELN     Field is mapped from order header
    3     Customer PO     VBKD-BSTKD     Field is mapped from order header
    4     Ship To     KUWEV-KUNNR     "This is field is mapped from order header to delivery header
    Ship to need to populate the fields below"
         Ship to Name          
         Ship to Address          
         Ship to City, State, Postal Code          
    5     Material No     LIPS-MATNR     Field is mapped from delivery item level
    5a     Legacy Item #     MARA-ZZQNUM     Field is mapped from material master
    6     Description     LIPS-ARKTX     Field is mapped from delivery item level
    7     Ship Qty     LIPSD-PIKMG     Field is mapped from delivery item level
    8     Unit of Measure (UOM)     LIPSD-VRKMP     Field is mapped from delivery item level
    9     Pallets     VEKP-EXIDV     Count of VEKP-EXIDV for LIPS-MFRGR
    LAYOUT
    Whs. BOL:                Customer PO:                    
    Order No:                                   
    Ship to:                                    
    Material No     Description     Ship Qty     UoM          Pallets          
    010018500013850003     16OZ 1/12 LPT ICED TEA PEACH       216     CS          2.00          
    904560                                   
    010018500013850005     16OZ 6/2 LPT ICED TEA RASP       108     CS          1.00          
    904561                                   
    010018500013850006     16OZ 6/2 LPT ICED TEA SNL       324     CS          3.00          
    904562                                   
    010018500013850007     16OZ CAN 1/12 MTN DEW AMP       118     CS          1.00          
    904563                                   
         POINTS WILL BE AWARDED TO ALL ANSWERS

    Hi,
    In form interface u have to define the fields or tables which all are u passing from the program.
    In the glabal definitions  you can define your types for internal tables or other purposes in 'TYPES' tab, then declare the global datas your internal tables, work areas etc.
    write ur select statement and othe codings there in initializations, define subroutines in form routines,
    then, u cna use loops , command lines for additional purpose in each pages.

  • Output determination for Shipping order confirmation

    Hi,
    Im new to the SD module.
    I want to send the BOL  information to XI as idoc DESADV.DELVRY03.
    How am i supposed to do this? Should i create a new Output type?
    I guess since im sending this to XI i should maintain the partner function as LS right?

    Ive uploaded a document on the steps i have done for setting up a Output type at:
    http://www.scribd.com/full/16969034?access_key=key-1tw12d6pow1xa4r6afcs
    or
    http://www.scribd.com/doc/16969034/Output-Determination-for-Delivery
    Still im not successfull in generating the IDOC. Please help.

  • EDI for Railway BOL

    Has anyone here done EDI for Railway Bill of Lading? I would appreciate some help from someone who's done this before. Thank you.

    Hi ,
    i can help you in this topic but what exactly you need .
    As per your concept  EDI Railway BOL , first of all you need to undestand/Describe of iDoc In the hence (CONTROL/DATA/STATUS-Records) .
    In  your requirement  you need to use Basic type SHPMNT04 .
    Carriers are assigned to the shipment as per routing matrix that . Exceptions in assigning carriers are considered wherever trade partner preferred carrier is to be considered.
    for your requirement some objects are required.
    1. Message types .  2. Create Condition record for Shipment Type.
    3. Partner profile for vendor  Railway  created in WE20 to processing  output.
    4. communication set up with Railway for sending EDI  messages and receiving EDI messages.
    5. EDI MAP for translating SHPMNT04 idocs into EDI  messages.
    This is some what  answer for your question . if you send exact requirement then i can give fruiful answer .   Thank you.
    Thanks & Regards
    Ramana

  • Should Output parameters always be declare at the beginning of the Stored Procedure?

    Should Output parameters always be declare at the beginning of the Stored Procedure?

    Usually input parameters listed first followed by output parameters. This is just a custom, not a requirement.
    Blog: How to architect stored procedure parameters?
    BOL: http://msdn.microsoft.com/en-us/library/ms187926.aspx
    Kalman Toth Database & OLAP Architect
    SQL Server 2014 Database Design
    New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

  • Formatting printer output for dotmatrix printer

    Hi Experts,
    i'm trying to format the output of the EPSON LQ-870 dot matrix printer to print the output in the paper size height 280 mm & width 210 mm.The device type i used for my output device is EPESCP2.For the first page the header and line items are coming correctly.But for the second page onwards, there is some space is coming between each line items.In third page,the header is coming little bit down from the required location.My page size is little bit less than the normal A4 size.How to rectify this?
    Points will be rewarded if helpful.......
    Thanks in advance.

    Hello,
    I created a condition table '550 - Shipping point/plant'. Then I created an access sequence 'ZSH1' and assigned this condition table 550 to it.
    In the output determination procedure, the procedure 'V10000 - Header output' has the condition type PL02 - BOL: Single Delivery assigned to it.
    The assignments look like:
    Step       Counter         Cond Type
    10               1                LD00     Delivery Note
    20               2                PL00     Packing list
    30               3                PL01     Planning Slip
    40               4                PL02     BOL: Single Delivery
    In Assign output procedures, the entry corresponding to delivery type 'LF' is:
    Del Type                O/P procedure                       O/P Type
    LF Delivery                    V10000  Header Output             LD00Delivery Note
    When I try to enter a new condition record using VV21, it does not show up this key combination 'Shipping point/Plant'.
    Can someone tell me if I am missing some customization?
    Thanks,
    Rugmani
    Edited by: Rugmani Rajan on Oct 22, 2008 3:06 PM

  • StatementText from ShowPlanXML only outputs 4000 characters?

    Hi, 
    It seems that StatementText in the ShowPlanXML only returns 3999 characters, even if the statement is larger than that.
    I have not seen this documented in the ShowPlanXML schema (http://schemas.microsoft.com/sqlserver/2004/07/showplan) or in the BOL. 
    Is there any way to get the complete SQL statement from the query plan?

    hi ，saso_k
    I found some clues in the MSDN
    http://msdn.microsoft.com/en-us/library/ms189747.aspx
    Under the following conditions, no Showplan output is returned in the query_plan column of the returned table for sys.dm_exec_query_plan:
    If the query plan that is specified by using plan_handle has been evicted from the plan cache, the query_plan column of the returned table is null. For example, this condition may occur if there is a time delay between when the plan handle was captured and
    when it was used with sys.dm_exec_query_plan.
    Some Transact-SQL statements are not cached, such as bulk operation statements or statements containing
    string literals larger than 8 KB in size. XML Showplans for such statements cannot be retrieved by using sys.dm_exec_query_plan unless the batch is currently executing because they do not exist in the cache.
    If a Transact-SQL batch or stored procedure contains a call to a user-defined function or a call to dynamic SQL, for example using EXEC (string), the compiled XML Showplan for the user-defined function is not included in the table returned
    by sys.dm_exec_query_plan for the batch or stored procedure. Instead, you must make a separate call to sys.dm_exec_query_plan for the plan handle that corresponds to the user-defined function. 
    When an ad hoc query uses simple or forced parameterization, the query_plan column will contain only the statement text and not the actual query plan. To return the query plan, call sys.dm_exec_query_plan for the plan handle of the prepared parameterized query.
    You can determine whether the query was parameterized by referencing the sql column of the sys.syscacheobjects view or the text column of the sys.dm_exec_sql_text dynamic management view. 

  • Delivery Output & Billing Output

    Hi All,
    Are there any standard transactions for Delivery and billing ouputs, other than VL02N & VF02
    So that user can view and take print outs of only those documents.
    Thanks & Rgds
    Naveen

    Hi Naveen
    DELIVERY OUTPUT:
    VL71    Output from Outbound Deliveries
    VL74    Output from Handling Units
    VL70    Output From Picking Lists
    VL75    Shipping Notification Output
    FOR GENERAL TRANSACTION CODE REFER BELOW:
    VL02N    Change delivery document
    VL04    Delivery due list
    VKM5    List of deliveries
    VL06G    List of outbound deliveries for goods issue
    VL06P    List of outbound deliveries for picking
    VL09    Cancel goods issue
    VT02N    Change shipment
    VT70    Output for shipments
    BILLING:
    VF02    Change billing document
    VF11    Cancel Billing document
    VF04    Billing due list
    FBL5N    Display Customer invoices by line
    FBL1N    Display Vendor invoices by line
    Create delivery via transfer orders
    Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
    VL04    Delivery due list. Run the delivery due with your order number to create the delivery
    LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
    The Transfer order should now be saved. It now needs to be confirmed.
    In LT03 go to menu option Transfer Order -> Confirm – Transfer Order
    Enter
    Save
    The transfer order is now confirmed.
    VL02N    Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit
    FOR ALL THE REQUIREMENT:
    Transactions
    search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
    EDI Specific Transactions
    VOE1    Translation between EDI categories and SD item categories
    VOE2    Table EDSC view. Customer link to sales area detail
    VOE3    Table view EDPVW. Add partner types that will be transferred to the IDoc
    VOE4    Table view EDPAR. Link external partner number with our internal number
    WEDI    EDI Administrator Menu
    BALE       Idoc Administration
    Scheduling agreements
    OVA9    Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
    OVAI    Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
    OVAJ    If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
    IDoc Transactions
    WE09 / WE02    IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
    WE05    View IDocs
    WE19    EDI test tool. Use to test inbound Function module changes.
    WE20    Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
    WE30    Create IDoc extension type
    WE31    Segment create
    WE57    Assign function module to logical message and IDoc type
    WE60    IDoc type documentation tool
    WE82    Link Release detail to Extension IDoc Type
    BD55    Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
    BD87    Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
    BALA    ALE Application Distribution
    BALM    ALE Master Data Distribution
    Output determination
    856 - ASN
    V/36   Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments
    VV21,VV22,VV23   Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21
    VL71   Reissue output for deliveries
    810 - Invoice
    V/54   Maintain access sequence for billing documents
    VV31,VV32,VV33   Create condition records for billing documents. (RD00 – RE Billing party)
    VF31   Reissue output for billing documents
    855 – Order Response
    V/30   Sales document output types (BA00)
    V/48, V/32, V/43   Maintain access sequence for sales documents
    VV11,VV12,VV13   Create condition records for sales documents. (BA00 – SP Sold to party)
    Requirements coding
    V/27    Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
    Sales & Distribution
    Sales order / Quote / Sched Agreement / Contract
    VA02    Sales order change
    VA05    List of sales orders
    VA22    Quotation change
    VA32    Scheduling agreement change
    VA42    Contract change
    Billing
    VF02    Change billing document
    VF11    Cancel Billing document
    VF04    Billing due list
    FBL5N    Display Customer invoices by line
    FBL1N    Display Vendor invoices by line
    Delivery
    VL02N    Change delivery document
    VL04    Delivery due list
    VKM5    List of deliveries
    VL06G    List of outbound deliveries for goods issue
    VL06P    List of outbound deliveries for picking
    VL09    Cancel goods issue
    VT02N    Change shipment
    VT70    Output for shipments
    General
    VKM3, VKM4    List of sales documents
    VKM1    List of blocked SD documents
    VD52    Material Determination
    Workflow
    SWEAD    Event queue administration
    SWE2    Event type linkages
    SWE3    Event linkages
    PPOME    Organizational Unit Maintenance
    SWE5    Consistency Checks for Event Linkages
    SWUD    Workflow Diagnostic Tool
    General
    The following section provides detail on other useful SAP areas.
    Create delivery via transfer orders
    Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
    VL04    Delivery due list. Run the delivery due with your order number to create the delivery
    LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
    The Transfer order should now be saved. It now needs to be confirmed.
    In LT03 go to menu option Transfer Order -> Confirm – Transfer Order
    Enter
    Save
    The transfer order is now confirmed.
    VL02N    Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit
    Purchase Orders
    ME22N      PO Change
    ME57         Create PO from purchase requisition
    Goods Movement
    MIGO    Post goods receipt
    Other
    MD04    Material Requirements. Shows material requirements and releases against materials
    SE38    ABAP Editor. Used to modify ABAP programs
    SM01    Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
    SHDB    Transaction recorder (BDC)
    CMOD    User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
    SE16    Table contents display
    SOST    View mails sent externally from SAP
    SU53    Check authorization object
    SQVI    Table Quickviewer – Used to created quick client dependent reports
    ST22    ABAP Dump Analysis
    ST01    System trace
    ST11   Display developer trace
    ST05          SQL Trace
    SM21          System log
    ST22           Display short dumps
    SM12          Display locked entries 
    Programs
    List of ABAP Reports
    Idoc
    RBDAPP01   Post inbound Idocs to application documents
    RBDAGAI2   Re-processing of IDocs after ALE input error
    RBDAGAIE   Reprocessing of edited IDocs
    RBDMANIN   Start error handling for non-posted Idocs
    RSEINB00   Idoc inbound processing by file
    RSEOUT00   Process outbound IDocs
    General
    RV80HGEN    Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.
    RSWUWFML    Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status' sent from SAP.
    RHSOBJCH    Corrects the following error in workflow customizing:
    Transport object PDST
    Information Table SOBJ is consistent as regards key tables
    **Error** Table HRP1600 Not an entry in table SOBJ
    Information Table SOBJ is consistent as regards PAD tables
    See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
    RSPO0075    Run report RSPO0075 to activate access method M for device types.
    Reward if useful to u
    Message was edited by:
            narendran vajravelu

  • Printer determination for sapscript form output

    Hello All,
    We have configured different printers for the different plants in our sales organization.  When we create a delivery, there is a requirement to send the delivery form output (bill of lading, delivery note etc.) to the appropriate printer based on the plant for which the delivery is created.
    Is it possible to do this and if yes, how should this be done?
    Any help will be greatly appreciated.
    Thanks in advance,
    Rugmani

    Hello,
    I created a condition table '550 - Shipping point/plant'. Then I created an access sequence 'ZSH1' and assigned this condition table 550 to it.
    In the output determination procedure, the procedure 'V10000 - Header output' has the condition type PL02 - BOL: Single Delivery assigned to it.
    The assignments look like:
    Step       Counter         Cond Type
    10               1                LD00     Delivery Note
    20               2                PL00     Packing list
    30               3                PL01     Planning Slip
    40               4                PL02     BOL: Single Delivery
    In Assign output procedures, the entry corresponding to delivery type 'LF' is:
    Del Type                O/P procedure                       O/P Type
    LF Delivery                    V10000  Header Output             LD00Delivery Note
    When I try to enter a new condition record using VV21, it does not show up this key combination 'Shipping point/Plant'.
    Can someone tell me if I am missing some customization?
    Thanks,
    Rugmani
    Edited by: Rugmani Rajan on Oct 22, 2008 3:06 PM

Maybe you are looking for