Create Print Output on Delivery Document

Hi everyone!!
Could you explain to me the configuration process for having a new output type to be trigered on a delivery document.
I want to name my output ZBXX.
Using a program to print called ZVXXPRNCFD and a smartform called ZVME_PRNCFD.
My output is going to be trigered by sap standard program RSNAST00.
Having that info, what else I need to configure to have it working?
Thanks in advance!!
Moderator message : Not directly related to ABAP Development. Post the question in relevant functional forum. Thread locked
Edited by: Vinod Kumar on Jul 13, 2011 11:09 AM

Oh, OK.
Your issue is in the program RV56ABST and its selection variant I guess. Try and view the action profile log for possible failures.
Also check if there are any requirements for those outputs which are not being met. Long shot.
Suggest raise an OSS message as it could be really a bug ( because it happens the first time) and SAP will attend to it.
Check out some other (older releases) for whatever they me worth:
426546 - Variant maintenance for report RV56ABST: Processing modes

Similar Messages

Output for Delivery Document

Dear Friends,
I could see output determinations maintained only for sales document,billing document,sales activities.....if delivery note has to be given then output determination sud b maintained for delivery document ryt.....why theres no determination for delivery doc?....Thanks in advance

Dear S Kumar,
Check with:
T. Code: V/36 - Maintain output determination for deliveries
V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 u2013 V7ALLE u2013 SHAD for grouped ASNs. I.e. Group deliveries into shipments
T. Code: VV21,VV22,VV23 - Create output condition records for shipping.
LAVA u2013 WE (Partner function) - We must add each new partner with VV21
T. Code: VL71 - Reissue output for deliveries
Best Regards,
Amit

Reg: COA Output for Delivery Document

Dear Gurus,
While creation of COA Output we need to enter the Delivery document.
I need to find out a Material in a Delivery Document for which the Inspection results are available
Is there any link between Delivery document and the Inspection results with respect to a Material?
Is it stored in any Table?
Regards.
RK

Can you expand on your problem a bit?
The delivery number and order numbers are available values in the standard COA program and are in the example COA SAPscript form. They are printed on the example COA.
Do you need this info to be used in another manner besides printing the info on the COA? Because that functionality is already there.
Craig

Printing output on word document

i[b] want to print the output on word document .
i saved the data in the file so that should be printed on word document.

on the button1_action() type the following :
FileWriter out = new FileWriter("c:/MyFile.rtf");
out.write("Your data is here......................");
out.close();hope this will help
good luck
mohammed

Delivery document Output Problem.

Hello Gurus,
I dont want to take the print ouot of delivery document if that delivery document is not PGI.
Is there a standard config setting for this.
Regards
Prashant

Hi
Kindly go through the below path and assign the routine "1" against the condition type in the out put procedure
Logistics Execution
Shipping
Basic Shipping Functions
   Output Control
     Output Determination
      Maintain Output Determination for Outbound Deliveries
        Maintain Output Determination Procedure
Regards
Damu

Outputing delivery document details in Script

HI all ,
we are using a script to output the Delivery document details .
Now the order of Item details in main window is based on handling unit no's used while packing . My requirement is instead of giving in the order they pack , customer want to output them in the order of line Item no packed .
EX : I haveLine items 10 , 20 , 30 , 40.   they are packed in handliong units 3 ,2 4,1 .
The current order printing is
ITEM    HANDLING UNIT
40              1
20              2
10              3
30              4 .
Now the customer needs , handling units that packed the ITEM no 10 to first and then line item no 20 ... like that .
expected order is
10              3
20              2
30              4
40              1 .
1) Have seen any document printing like this .   Output in terms of line items rather to order of handling units , whille packng .Is it posiible?
I debugged the script and found that SAP Print progarm passing the details to scrpt in the order of Handling units one at time through structure VBPLP and VBPLK , where as in script we cacth that info and dprint on layout .I Feel the order is controlled at Print prog level not at script level . when it calling script for first time , the details avilable in structure are about handling unit 1 and corresponding item (40) details , and then for 2 ,3 ... at last for 4(Item no 30 ) . Please comment .Please guide me if You have ever faced this kind of scenario.

Hi Dharma,
You can simply sort your internal table with line item no. So, when you will loop at the table, it will print the first line item first(And this is ur requirement).This will solve your problem.
Hope this helps.
Regards,
Richa

How to create new documet from the output of another document automatically

Hi all
here is the scenario, If we are creating an debit memo request and debit memo to a customer, from the output of this debit memo we need to trigger the creation of another document( Ex credit memo to another customer) automatically, how we can do this?

Hi Dev,
You need to create another report program for the other document along with the smartform.
In the report program, you have to put your logic on how the other document has to be found when your document is created and the output be triggered.
So in principle,
There will be two programs linked to your output type.
One will create the output of the document which is being created,
Another program will automatically call the other target document in change mode and trigger the same output, during which the second program will be executed.
Now the second program will create the output for the second document.
Making copy controls wont help for this reqmt.
Reward points if it helps.

Disable print output when using bapi BAPI_GOODSMVT_CREATE

Hello,
I am using BAPI BAPI_GOODSMVT_CREATE to post material documents in our programs.
I wish to prevent the print output of the documents created by the BAPI.
Meaning - when the user post good movement using MIGO, there will be a printout of the movement, but if the movement is created using BAPI_GOODSMVT_CREATE, no output will be printed.
I have tried sending blank values in fields VER_GR_GI_SLIP & VER_GR_GI_SLIPX in GOODSMVT_HEADER structure, but to no avail.
Is there a way to disable printing ONLY when using the BAPI?
Thank you very much.

Hi,
We cant restrict the print preview or print out of the material document. Once the condition record has maintianed for the material document, it ll applicable for all the material doc . It would be manual Gr or BAPI GR.
In your case Print is coming automatically or user is taking the print !!
Regards,
Dhanush.

Posting GR against inbound delivery document by MIGO for the movt type 101

Hello Team
To put my question in a simple way, i have changed the subject also. my requirement as below.
In my legacy system GR against PO is happening and the same data is passing to SAP system through PI. Where i need to post GR against the inbound delivery document of that PO.
I followed the below steps
1. i have used idoc mbgmcr03 and copied the FM ZIDOC_INPUT_MBGMCR.
2. In PI system i am doing all relavent mappings.
Now i want to retrieve the inbound delivery document from SAP for the PO which i got from legacy system. Then i need to post the GR against that inbound delivery document. Finally IDOC should gets created with that inbound delivery document details.
So please let me know the procedure to follow to resolve my issue.
Thanks in advance.
Regards
Sree
Edited by: sree@technical on May 11, 2010 5:20 PM

Hi
As far as my experiance with SAP says we don't have any SAP Standard setting to update the entry related to T-code. Internally all the ABAP code reads the t-code and based on the processing type define it execute the code and update the table so that later analysis can be done by which t-code the document got generated

Serial no in delivery document

Hi to all,
i am facing some problem regarding print layout in delivery document .i want serial no in delivery doument.because serial no is print on separate page.i want print serial no. on delivery document .if i set serial no in prinlayout. it does not show serial no database table in delivery document...pls help me...
Regards,
vishal

HI,
IN 2007 version you can print the serial numbers. See the system PLD-s names "Delivery Including Batch/SN (System)"
Regards,
J.

Credit data refresh on delivery document

Hi
I've noticed that the credit data (Risk category / Customer credit group etc) on an SD delivery document is copied over from a sales order.
Is it possible to have the credit data refreshed from the credit master when a delivery document is created?
This is required in cases when the risk category is changed after an order is created and before a delivery document is created.
Sequence:
VA01: Order is created (VBAK-CTLPC = 01 for example)
FD32: Risk category is changed (from 01 to 02 for example)
VL01n: Delivery is created (As per current settings, CTLPC on the delivery is 01, it is required that we get 02 instead)
Kindly suggest any solutions
Thanks,
VH

Dear Vicky,
I doubt that if it can be achieved through configuration, although with the help of an ABAPer you can write a requirement in copy control to compare the existing Risk Category and if found different overwrite with the one recently maintained.
Hope solves your problem
Regards,
Paresh

Output types for delivery documents

Hi All,
Please help me out.
Thanks in advance,
Here i got a requirement like i already have the output types for the delivery documents.However i need to copy the existed output types into different names bcoz to customize it for different organization in different region.
The problem is i already copied the o/p types but when i went to vl03n and tris to see the output , am not able to find my o/p type there...am i need to do anything more..
Please help me out as i am a ABAPER and not the functional guy am facing lot of difficulty...
again thanks in advance.

dear govardhan
please refer below
Output Determination Procedure
Output is a form of media from business to one of its business partners. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of Order Confirmations, Freight List, Delivery Notes, Invoices & Shipping Notifications. Determining form of output is output determination
Types of Output: Print Output, Fax, Telex, E-Mail & EDI (Electronic Data Interchange)
PRINT OUTPUT:
SPRO- IMG- Basic Functions- Output Control- Output Determination- Output Det using Cond Tech- Output Det for Sales Documents & output determination for billing documents.
Create Condition Table: select the field Sales Doc Type from field catalog & Save
Maintain Access Sequence: 4-digits code & description. Assign condition table to access sequence. Select Accesses line item and Goto Fields. Fields will display the fields we have selected in the condition table i.e. sales doc type.
Select BA00 & Copy & Rename. Give the same 4-digit code as given to acc seq.
You Can Maintain:
Languages of Output
Partners (to whom we want to send output)
Print Program- print specification
Sap Script- layout
Assign Output Types to Partner Functions: go to new entries & assign your output type to partner functions.
Maintain Output Determination Procedure: V10000 (Standard Procedure). Go to new entries & create your own 6-digit code with descp. Select the procedure & go to Control Data. Here mention the output type i.e. cond type & leave requirement and manual only columns as blank.
Determination Rule: link the 6-digit procedure code to doc types.
Create Condition Records: VV11. Select document type and click on Communication. Mention partner function, medium, time. Output device: LP01, Spool request Name: SD_003, Suffix 2: order_confir & flag on print immediately.
Once you press enter you will come across 2 key combinations:
Sales organization/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to whom the output should be sent, time, medium, language. {It contains: Sales Orgn, Customer, Partner Function (The abbreviated form of the name that identifies the Partner) (During output determination, the system determines the recipient of the output from the master record for the specified partner function. In this field, you can explicitly specify a recipient that will override the standard partner. There must also be a master record for the partner that is specified explicitly.), Medium, Time & Language.}
Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time & Language.
In SAP we can send the documents to respective partner functions through different transmission mediums. SAP uses condition technique to determine output t relevant partners with relevant transmission mediums.
Out put determination procedure has a integration with technical module, as ABAPers has to write SMART forms and FORMS to print the output , that SMART form output can be send to relevant partner function through relevant transmission mediums.
Out put determination procedure for order confirmation: (V/57)
a) Maintain condition table:
Path:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain condition tables
Maintain out put condition table for sales document
Here we define condition table
Ex: 007 order type (sales order types)
Save it
b) Maintain output types:
IMG
SD
Basic functions
Output control
Output determination
Output determination using the condition technique
Maintain out put determination from for sales document
Maintain out put types
Here we define out put types
Ex:     AF00 -- Inquiry
     AN00 quotation
     BA00 Order confirmation
     BA01 EDI odd response
     KRMLCredit processing
     LP00 -- Scheduling agreement
     MAIL Internal message
     RD03cash sales invoice
Choose BA00 copy it and rename as a MA00
click on details icon
click on display to change icon
then again choose MA00 click on details icon
Maintain data in general data tab
General data tab:
Access sequence: 0010(order type)
In IMG define access sequence and assign to the output type
Check access to conditions:
     This indicator allows the system to read the condition records for output. If it is not been activated then system determines out put from customer master ex: By following out put determination procedure DB0001
Check cannot be changed:
     This control specifies whether the out put can be changed or not
Ex: direct mailings can be changed during processing
Check multiple issuing:
This indicator allows the system to send the output multiply
Ex: sales order has been sent for 10 items again one item has been added to sales order so that business has to issue the new out put for sold to party with added line items. This indicator allows the system to send out put repeatedly.
Check partner independent out put:
During output processing when the indicator has not set then system allows only specific functions in specific partner functions
Dont write processing:
This indicator determines whether system has to write processing log for output
Default values tab:
Dispatch time:
Ex: send immediately: when carry the application this indicator determines when the output should be sent.
Transmission medium:
Ex:     print out
     Fax
     Telex
     Internal send
     EDI
     Simple mail
     Special function
     Events (SAP business workflow)
     Distribution (ALE)
     Tasks (SAP business work flow)
Specify the transmission medium through which the output should be sent. (Ex: print output)
Communication strategy
Specify the communication strategy if you want to send the output externally
A) Time tab:
Check timing: (Periodic job not allowed)
This indicator allows the system to carry out print program periodically.
B) PRINT NEXT TAB):
Print parameter: Ex sales org.
     Specify the print parameter.
Click on mail title & Text control button under dialog structure.
Here we assign title for the mail along with relevant text Ex:-EN (English)
Processing routines control button under dialog structure.
Here we assign programs form routines & form that are written by ABAPER, they           they various transmission mediums.
Ex; - Transmission medium      shortest      program     form routine
          1                  print out     RVADOR       entry
Click on position function control button here we assign relevant partner function to relevant transmission mediums
          EX: print out: SP (Sold to party)
C) Maintain access sequences:
     Here we define Access sequence.
EX: 0010 & Assign the condition tables to this output.
D) Assign out put types to partner function:
     Here we assign output types along with transmission mediums to relevant partner functions.
EX:      Out put type          Transmission medium
       MA00                    1
                              2
                              6
                              A
       MAIL                    7
E) Maintain output determination procedure:
     Here we define output determination procedure
Ex:     V10000     -     Order output
     V05000     -     Inquiry output
     V06000     -     quotation output
     V10001     -     Cash sales output
Choose output determination procedure EX; V10000, copy it& rename it as MA0000
Assign output type MA00 by going control date section.
Save it.
F) Assign output determination procedures;
Allocate sales document Header.
_ Choose sales document type OR & Assign output determination procedure i.e MA0000 & Assign output type MA00.
Assign sales document items.
-Choose item category TAN & Assign output determination procedure Ex: Ma0000
- save it & exit.
Maintain output records (vv11)
Path:
Logistic > S&D > Master data > output > sales document > VV11 Create
Specify output MA00, Click on Key combination & specify sales document type (OR), partner function (sp) transmission medium (1) dispatch type (4) language (EN)
Click on communication button on application tool bar
Specify output device LOCL or LP01
Check print immediately check release after output
Save it
Go to Va01 raise the sales order
Go to extra button output header edit.
Specify output type: MA00 partner function
Select line, click on communication methods
Specify logical destination
Check print immediately
Check release after output
go back save it & exit
Go to VA02, Go to Extras output header print preview
Check out (order confirmation
(ERROR: out put MA00 for partner cannot be processed)
rewards pls
siva

How 2 creat report for displaying the details of a Delivery Document using

how to create report for displaying the details of a Delivery Document using the tables LIKP, LIPS
thank you
regards,
jagrut bharatkumar shukla
points will be rewarded

HI
I AM GIVING YOU MY DELIVERY DOCUMENT CODE...MODIFY IT ACCORDING TO YOUR REQUIREMENT
*& Report ZDELIVERY                                *
report zdelivery message-id z9bhu          .
types: begin of t_likp,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
*           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
*           WAERK TYPE LIKP-WAERK,      "Currency
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
       end of t_likp.
types: begin of t_lips,
           vbeln type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,
*           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
           vgbel type lips-vgbel,      "Doc no of the reference document
        end of t_lips.
types: begin of t_vbpa,
           vbeln type vbpa-vbeln,      "SD DocumenT Number
           posnr type vbpa-posnr,      "Item number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,      "Customer Number 1
       end of t_vbpa.
types: begin of t_kna1,
           kunnr type kna1-kunnr,      "Customer Number 1
           name1 type kna1-name1,      "Name 1
           ort01 type kna1-ort01,      "City
           adrnr type kna1-adrnr,      "Address
       end of t_kna1.
types: begin of t_li_vbpa,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
*           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
*           WAERK TYPE LIKP-WAERK,      "Currency
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
           vbeln1 type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,      "Net Price
*           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
           vgbel type lips-vgbel,      "Doc no of the reference document
           vbeln3 type vbpa-vbeln,     "SD DocumenT Number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,      "Customer Number 1
       end of t_li_vbpa.
types: begin of t_final,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
           vbeln1 type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,      "Net Price
           vgbel type lips-vgbel,      "Doc no of the reference document
           vbeln3 type vbpa-vbeln,     "SD DocumenT Number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,     "Customer Number 1
           name1 type kna1-name1,      "Name 1
           ort01 type kna1-ort01,      "City
           adrnr1 type kna1-adrnr,     "Address
           name2 type kna1-name1,      "Name 1
           ort02 type kna1-ort01,      "City
           adrnr2 type kna1-adrnr,     "Address
           name3 type kna1-name1,      "Name 1
           ort03 type kna1-ort01,      "City
           adrnr3 type kna1-adrnr,     "Address
       end of t_final.
*            D A T A D E C L A R A T I O N
*&*********Internal Table Declaration****************&*
data: it_likp type standard table of t_likp.
data: it_lips type standard table of t_lips.
data: it_vbpa type standard table of t_vbpa.
data: it_kna1 type standard table of t_kna1.
data: it_li_vbpa type standard table of t_li_vbpa.
data: it_li_vbpa_temp type standard table of t_li_vbpa.
data: it_final type standard table of t_final.
*&*********Work Area Declaration********************&*
data: wa_likp type t_likp.
data: wa_lips type t_lips.
data: wa_vbpa type t_vbpa.
data: wa_kna1 type t_kna1.
data: wa_li_vbpa type t_li_vbpa.
data: wa_li_vbpa_temp type t_li_vbpa.
data: wa_final type t_final.
*&*********Data Declaration************************&*
data: d_vbeln type likp-vbeln.
data: flag type i value 0.
*           S E L E C T I O N S C R E E N   D E C L A R A T I O N
selection-screen begin of block block2 with frame title text-001.
select-options: s_vbeln for d_vbeln obligatory.    "Delivery no
selection-screen end of block block2.
*            A T S E L E C T I O N - S C R E E N   E V E N T S
*AT SELECTION-SCREEN.
*PERFORM VALIDATE_DATA.
*            S T A R T   O F S E L E C T I O N     E V E N T S
start-of-selection.
perform fetch_data.
perform merge_data_kna1.
*INCLUDE Z9BT_SH_***4_FORMS.
call function 'OPEN_FORM'
exporting
*   APPLICATION                       = 'TX'
*   ARCHIVE_INDEX                     =
*   ARCHIVE_PARAMS                    =
    device                            = 'PRINTER'
*   DIALOG                            = 'X'
*   FORM                              = ' '
   language                          = sy-langu
*   OPTIONS                           =
*   MAIL_SENDER                       =
*   MAIL_RECIPIENT                    =
*   MAIL_APPL_OBJECT                  =
*   RAW_DATA_INTERFACE                = '*'
*   SPONUMIV                          =
* IMPORTING
*   LANGUAGE                          =
*   NEW_ARCHIVE_PARAMS                =
*   RESULT                            =
exceptions
   canceled                          = 1
   device                            = 2
   form                              = 3
   options                           = 4
   unclosed                          = 5
   mail_options                      = 6
   archive_error                     = 7
   invalid_fax_number                = 8
   more_params_needed_in_batch       = 9
   spool_error                       = 10
   codepage                          = 11
   others                            = 12
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
sort it_final by vbeln.
loop at it_final into wa_final.
call function 'START_FORM'
exporting
*   ARCHIVE_INDEX          =
   form                   = 'Z9BT_DELIVERY'
   language               = sy-langu
*   STARTPAGE              = ' '
*   PROGRAM                = ' '
*   MAIL_APPL_OBJECT       =
* IMPORTING
*   LANGUAGE               =
exceptions
   form                   = 1
   format                 = 2
   unended                = 3
   unopened               = 4
   unused                 = 5
   spool_error            = 6
   codepage               = 7
   others                 = 8
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function 'WRITE_FORM'
exporting
   element                        = 'ITEM_LIST'
   function                       = 'SET'
   type                           = 'BODY'
   window                         = 'MAIN'
* IMPORTING
*   PENDING_LINES                  =
* EXCEPTIONS
*   ELEMENT                        = 1
*   FUNCTION                       = 2
*   TYPE                           = 3
*   UNOPENED                       = 4
*   UNSTARTED                      = 5
*   WINDOW                         = 6
*   BAD_PAGEFORMAT_FOR_PRINT       = 7
*   SPOOL_ERROR                    = 8
*   CODEPAGE                       = 9
*   OTHERS                         = 10
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function 'END_FORM'
* IMPORTING
*   RESULT                         =
exceptions
   unopened                       = 1
   bad_pageformat_for_print       = 2
   spool_error                    = 3
   codepage                       = 4
   others                         = 5
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endloop.
call function 'CLOSE_FORM'
* IMPORTING
*   RESULT                         =
*   RDI_RESULT                     =
* TABLES
*   OTFDATA                        =
exceptions
   unopened                       = 1
   bad_pageformat_for_print       = 2
   send_error                     = 3
   spool_error                    = 4
   codepage                       = 5
   others                         = 6
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
*&      Form VALIDATE_DATA
*       text
* --> p1        text
* <-- p2        text
form validate_data .
select single vbeln into wa_likp-vbeln
                    from likp where vbeln in s_vbeln.
append wa_likp to it_likp.
if sy-subrc <> 0.
flag = 1.
endif.
endform.                    " VALIDATE_DATA
*&      Form FETCH_DATA
*       text
* --> p1        text
* <-- p2        text
form fetch_data .
select a~vbeln
       a~erdat
       a~kunnr
       a~kunag
       a~traty
       b~vbeln
       b~posnr
       b~matnr
       b~arktx
       b~lfimg
       b~netpr
       b~vgbel
       c~vbeln
       c~parvw
       c~kunnr
         into table it_li_vbpa
                from likp as a
                left outer join lips as b on a~vbeln = b~vbeln
                inner join vbpa as c on b~vgbel = c~vbeln
                where a~vbeln in s_vbeln and
                c~parvw = 'RE'.
endform.                    " FETCH_DATA
*&      Form MERGE_DATA_KNA1
*       text
* --> p1        text
* <-- p2        text
form merge_data_kna1 .
if it_li_vbpa[] is not initial.
it_li_vbpa_temp[] = it_li_vbpa[].
sort it_li_vbpa_temp by kunnr.
delete adjacent duplicates from it_li_vbpa_temp comparing kunnr.
loop at it_li_vbpa into wa_li_vbpa.
read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
wa_li_vbpa-kunag.
if sy-subrc <> 0.
wa_li_vbpa_temp = wa_li_vbpa.
append wa_li_vbpa_temp to it_li_vbpa_temp.
endif.
read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
wa_li_vbpa-kunnrb.
if sy-subrc <> 0.
wa_li_vbpa_temp = wa_li_vbpa.
append wa_li_vbpa_temp to it_li_vbpa_temp.
endif.
endloop.
endif.
if it_li_vbpa_temp[] is not initial.
select kunnr
        name1
        ort01
        adrnr into table it_kna1 from kna1
                    for all entries in it_li_vbpa_temp
                    where kunnr = it_li_vbpa_temp-kunnr.
endif.
loop at it_li_vbpa into wa_li_vbpa .
wa_final-vbeln = wa_li_vbpa-vbeln.
wa_final-erdat = wa_li_vbpa-erdat.
*it_final-LFART = it_li_vbpa-LFART.
wa_final-kunnr = wa_li_vbpa-kunnr.
wa_final-kunag = wa_li_vbpa-kunag.
*it_final-VSTEL = it_li_vbpa-VSTEL.
wa_final-traty = wa_li_vbpa-traty.
wa_final-vbeln1 = wa_li_vbpa-vbeln.
wa_final-posnr = wa_li_vbpa-posnr.
wa_final-matnr = wa_li_vbpa-matnr.
wa_final-arktx = wa_li_vbpa-arktx.
wa_final-lfimg = wa_li_vbpa-lfimg.
wa_final-netpr = wa_li_vbpa-netpr.
*wa_final-GEWEI = it_li_vbpa-GEWEI.
*it_final-VOLUM = it_li_vbpa-VOLUM.
*it_final-VOLEH = it_li_vbpa-VOLEH.
wa_final-vgbel = wa_li_vbpa-vgbel.
wa_final-vbeln3 = wa_li_vbpa-vbeln.
*wa_final-PARVW = wa_li_vbpa-PARVW.
wa_final-kunnrb = wa_li_vbpa-kunnrb.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnr.
if sy-subrc = 0.
wa_final-name1 = wa_kna1-name1.
wa_final-ort01 = wa_kna1-ort01.
wa_final-adrnr1 = wa_kna1-adrnr.
endif.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunag.
if sy-subrc = 0.
wa_final-name2 = wa_kna1-name1.
wa_final-ort02 = wa_kna1-ort01.
wa_final-adrnr2 = wa_kna1-adrnr.
endif.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnrb.
if sy-subrc = 0.
wa_final-name3 = wa_kna1-name1.
wa_final-ort03 = wa_kna1-ort01.
wa_final-adrnr3 = wa_kna1-adrnr.
endif.
append wa_final to it_final.
clear wa_final.
endloop.
endform.

Delivery document how to print the BOM Parent and Child items

Hi,
I have a production BOM. In Delivery document how to print the Parent and Child items Item Code and Qty.At the time
of add a delivery document Inventory stock redused only in Parent Item not child item because child item stock already reduced in issue for production.

If you need to print both the BOM Parent and Child items, you have to create your own report. BOM is only for production if it is not Sales type.
Thanks,
Gordon

Table for output type of a delivery document

Hi guys,
Would you know where could I find the output type of a delivery document espcially after I posted a GI in Shipment? Basically, It should reflect in devlivery document. So I am not sure if I should look at the delivery tables or goods issue.
Help me guys!
POints for the helpful ideas.
THanks!

Hi,
There are 2things to be noted here.
1. If your output type was already triggered once, then it should be visible in display mode also, with a Green colour button (if it is processed and the print out is obtained). The fact that the output type is not seen in display mode, says that the output type so far has nto been triggered.
2. Seeing the output type coming in yellow colour in change mode of delivery document is expected. This means that the output is getting triggered now.If you save teh document now, you will get the print out.When you go in display mode again after a gap of say 1min, you can see the same output in Green colour as mentioned earlier.
I hope this clarifies your doubt.Please let me know if you need some more info
You can reward me if it helped you

Create Print Output on Delivery Document

Similar Messages

Maybe you are looking for