Qulaity Certificate "Output Type " for delivery

How does the working of Output Type LQCA & LQCB differ ?

Hi
LQCB: Sold to party means to whom you sold your product
LQCA Ship to party means to whom yo deliver the product.
Suppose your manufacturing team needs some material, so they ask Sales department to put order for that material to vendor A. Now for vendor A, sold to party is sales department to whom he sold and manufacturing team will be ship to party to whom he actually delivered the material. So ship to party receives goods ordered by sold to party.

Similar Messages

Output type for Delivery note missing for shipping point

Hi all,
   I have a plant setup to email delivery note which uses shipping point SGUS. Condition record is setup for this shipping point using Del Typ/Shipping Point /Plant. This uses the communication stragery ZINT.
The email works well for this shipping point. However, when delivery cannot be email using shipping point CHAL. I guess this plant has 2 shipping points (sgus and chal).
When delivery is created, output type for email is missing.   I already created condition rec
for LF/CHAL/plant 121. Still not working.
Can anyone pls provide any suggestions ASAP ?
Thanks
Joyce

Hi MdZ,
   I looked at the analysis output. ZD04 output is what i am after. Don't understand the followings:
Q1 - why the ordering in anaylsis is different than in output determination procedure. For example:
In Analysis Output: i have:
LDOO    - Output not found
MAIL     - manual output
PLOO    - Output not found
Z940    - Output found
ZBOL   - Output not found
ZD04   - OUTPUT NOT FOUND
The Output Determination Procedure as:
Step Counter   CType
10       1           LD00
12       1           ZLFX
13       0           LALE
14       1           ZBOL
20        2          MAIL
75       1           ZD04
90       1           PL00
110      1          Z940
Step 10 should be read , then step 12, and so on. Why is the ordering in procedure different than in
output analysis ?
Q2. Why did it display ZD04 not found when ZD04 appear on the delivery output as green light ? When i drill down, it show 2 access sequence. Access 10 stated Output found. Access 20 stated Output not found.
Thank you.
Joyce

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

Standard output type for Delivery picking list

Hi All,
My requirement is to trigger a picking list from the outbound delivery whenever the overall WM status is "B". Probably I need to look at a new requirement routine to add this condition.
Pls tell me what is the standard output type available for delivery picking list. I have analyed "EK00". Looks like this works only for deliveries without warehouse management.
Also we dont have a customization path for "EK00" and it has to be assigned to a shipping point.
Pls confirm if we can use EK00 for deliveries with warehouse management and is it correct?Else what is the other standard output type available for delivery picking list.

check ZPCK picking list.
SPRO>Logistics Execution>Shipping>Basic Shipping Functions>Output Control-->Define print parameters shipping
Here available ZPCK condition type.I think this condition record you can use.

WMTA output type for delivery note.

hey experts
we are using output type WMTA (automatic TA) for delivery note with Medium 8 (Special Function) & date/time 4 (send immdiately when saving appli).
In production server when user save delivery WMTA trigger with ZPLF(std delivery outpt type) in 2nd line and print the doc.
but
In Dev & Qas server when i save the delivery document. it only trigger WMTA and it is not printing the delivery note
i guess unless until WMTA not trigger with ZPLF printing is not possile.
i want know how WMTA output type trigger with ZPLF output type in Production Server.
Why WMTA not triggering the ZPLF in DEV & QAS.
thanks
Edited by: manojverma on Jul 2, 2011 4:40 PM

Hi MdZ,
   I looked at the analysis output. ZD04 output is what i am after. Don't understand the followings:
Q1 - why the ordering in anaylsis is different than in output determination procedure. For example:
In Analysis Output: i have:
LDOO    - Output not found
MAIL     - manual output
PLOO    - Output not found
Z940    - Output found
ZBOL   - Output not found
ZD04   - OUTPUT NOT FOUND
The Output Determination Procedure as:
Step Counter   CType
10       1           LD00
12       1           ZLFX
13       0           LALE
14       1           ZBOL
20        2          MAIL
75       1           ZD04
90       1           PL00
110      1          Z940
Step 10 should be read , then step 12, and so on. Why is the ordering in procedure different than in
output analysis ?
Q2. Why did it display ZD04 not found when ZD04 appear on the delivery output as green light ? When i drill down, it show 2 access sequence. Access 10 stated Output found. Access 20 stated Output not found.
Thank you.
Joyce

Delivery Schedule output type for change

Hi all,
i have created a custom output type for delivery schedule. i am using this output type to send IDoc. For create it is working fine. i have maintained condtion record as well.
whenever the delivery date and qty is changed, change output type is triggered but it fails there. the error shows no IDoc could be generated as there are no changes releveant to that.
i checked the configuration field relevant to printout changes, in that for table EKET-EINDT and menge i have checked the scheduling agreement. but here i could not find delivery schedule.
Can you please help on this..
Thanks

Hi
You need to confiugre output determination. Please check the below link.
Re: Email output of PO
output determination
Regards
Antony

Output Determination for Delivery doc

Hi Friends,
I am not able to see any output types maintained for delivery documents.......LD00 is the output type for delivery..so whr the setup exists in IMG?.....thanks in advance.....

Hi
You can go to NACE t-code to check for your output type. On the main screen, select "Shipping" and click on "Output Types" icon on top.
Search for your output type say LD00. You will be able to see what is the driver program against it and what form (standard SAP or customized) is attached to it for printing purpose.
Go to VV23 T-code and input your condition type LD00 and click on "condition info" and execute it. You will be able to see what condition records are maintained against that output type. If you dont get any entries then condition records have to be maintained. For this you can go to VV21 T-code and maintain the condition type LD00 for printing against any access sequence available in your system.
Hope this helps
Regards,
Syed Nasir

Output Type for Header

Hi All,
I have created an output type for delivery in intercompany scenario (STO). This is triggered at item level only when I create a delivery document with reference to a purchase order. At header level, it's not coming.What could be the reason? Please help.
Regards,
Raghav

Hi All,
I have created an output type for delivery in intercompany scenario (STO). This is triggered at item level only when I create a delivery document with reference to a purchase order. At header level, it's not coming.What could be the reason? Please help.
Regards,
Raghav

Output type for Proforma Invoice for return delivery from delivery type RLN

Client require Output type Proforma Invoice for return delivery to vendor. As such return item category is not relevant for pricing so from delivery to proforma invoice can not have with p-ricing. I got quantity correct but pricing is coming Zero.
Client have ZPAC as packing list output type from delivery which shows quantity and pricing. So decided to use the same logic to pull pricing for proforma invoice from delivery.
Here delivery has standard output ZPAC as packing list with access sequence Z002 as Delivery Type.
I want to pop up output type for all return delivery so using access sequence with delivery type/vendor.
Vendor filed does not exist in delivery output type so brought that firld LIFNR.
It is assigned to procedure and maintained ZPRO output type for Proforma invoice. Asigned VV21 on front end.
Problem Still automatic output type ZPRO is not poping up. What type of access sequence will help me to pop up or what in configuration am I miising?
Appreciate help for solution at earliest.

Hi Padamsree,
I know Pricing & output very well. I need profomra invoice to be printed with quantity & value for return goods to the vendor. Pricing is associated with Item category RLLN for delivery type RLL which is return type delivery.
I need to have pricing in my Proforma invoice which is copied from delivery to billing document VTFL. Just check well how it is working in the system & if you know please answer so that it should be workable on the system. As theoretical answer may not be helpful. Appreciate for your time.
Thanks

Output Type for Outbound Delivery in VL02N

Hi All,
Could you please tell me how to maintain output types for a specific outbound delivery in ECC , so that inbound delivery is created automatically from it? is it maintained in VL02N? I actually searched this on various forums but did not find the correct answer, as everywhere only the customizing is given.
Thanks in advance
Best Regards,
Abhijeet

Hi,
You can maintain the output type SPED as below. Once you do PGI, SPED should be processed. If not , do it manually from VL71.
VL02N -> Extra>Delivery Output -> Header> Output Type = SPED
Regards
Edited by: Shashidhar Shetty on Dec 5, 2011 1:59 PM

Output type for the managed codes cut letter is hard coded

Hello,
Very Good afternoon!
I have a requirement to create new Output Types for a Smart Form.
The already existing Output types are hard coded as shown Below :
CONSTANTS : c_kschl_order LIKE nast-kschl
                         VALUE 'ZUS0',
            c_kschl_order1 LIKE nast-kschl
                         VALUE 'ZUS1',
Now they do not want to use ZUS1. Insted they wnat to use New Output Types.
u2022 Remove ZUS1 as we no longer use this one.
u2022     Add ZAU0
u2022     Add ZNZ0
u2022     Add ZJP0
u2022     Add ZCN0
u2022     Add ZKR0
How to add these Output types without Hardcoding as shown ABove.
Any Suggestions will be appreciated.....
For reference..I will paste the code of the Program here.
Here is the code :
                 PROGRAM DECLARATION
PROGRAM ID           Z_RVADOR01_SALES_CUT_LETTER
TABLES: vbak,    "Sales Document: Header Data
       vbap,    "Sales Document: Item Data
       vbpa,    "Sales Document: Partner
       vbep,    "Sales Document: Schedule Line Data
       kna1,    "General Data in Customer Master
       MARA,    "Material Master
        KOMK,                          "Communicationarea for conditions
        KOMP,                          "Communicationarea for conditions
        KOMVD,                         "Communicationarea for conditions
        VBCO3,                         "Communicationarea for view
        VBDKA,                         "Headerview
        VBDPA,                         "Itemview
        VBDPAU,                        "Subitemnumbers
        CONF_OUT,                      "Configuration data
        SADR,                          "Addresses
        TVAG,                          "Reason for rejection
        VEDKA,                         "Servicecontract head data
        VEDPA,                         "Servicecontract position data
        VEDKN,                         "Servicecontract head notice data
        VEDPN,                         "Servicecontract pos. notice data
        RISERLS,                       "Serialnumbers
        KOMSER,                        "Serialnumbers for print
        TVBUR,                         "Sales office
        TVKO,                          "Sales organisation
        ADRS,                          "Communicationarea for Address
        FPLTDR,                        "billing schedules
        WTAD_ADDIS_IN_SO_PRINT,        "additional
        WTAD_BUYING_PRINT_EXTRA_TEXT, "texts belonging to additional
        adrc,
        adr6,
        t247.
INCLUDE RVADTABL.
INCLUDE RVDIREKT.
INCLUDE VEDADATA.
data for access to central address maintenance
INCLUDE SDZAVDAT.
TYPE-POOLS: ADDI.
DATA PRICE_PRINT_MODE(1) TYPE C.       "Print-mode
DATA: RETCODE   LIKE SY-SUBRC.         "Returncode
DATA: REPEAT(1) TYPE C.
DATA: XSCREEN(1) TYPE C.               "Output on printer or screen
DATA: BEGIN OF STEU,                   "Controldata for output
        VDKEX(1) TYPE C,
        VDPEX(1) TYPE C,
        KBKEX(1) TYPE C,
        KBPEX(1) TYPE C,
      END OF STEU.
DATA: BEGIN OF TVBDPA OCCURS 0.        "Internal table for items
        INCLUDE STRUCTURE VBDPA.
DATA: END OF TVBDPA.
DATA: BEGIN OF TKOMV OCCURS 50.
        INCLUDE STRUCTURE KOMV.
DATA: END OF TKOMV.
DATA: BEGIN OF TKOMVD OCCURS 50.
        INCLUDE STRUCTURE KOMVD.
DATA: END OF TKOMVD.
DATA: BEGIN OF TVBDPAU OCCURS 5.
        INCLUDE STRUCTURE VBDPAU.
DATA: END   OF TVBDPAU.
DATA: BEGIN OF TKOMCON OCCURS 50.
        INCLUDE STRUCTURE CONF_OUT.
DATA: END   OF TKOMCON.
DATA: BEGIN OF TKOMSERVH OCCURS 1.
        INCLUDE STRUCTURE VEDKA.
DATA: END   OF TKOMSERVH.
DATA: BEGIN OF TKOMSERVP OCCURS 5.
        INCLUDE STRUCTURE VEDPA.
DATA: END   OF TKOMSERVP.
DATA: BEGIN OF TKOMSERVHN OCCURS 5.
        INCLUDE STRUCTURE VEDKN.
DATA: END   OF TKOMSERVHN.
DATA: BEGIN OF TKOMSERVPN OCCURS 5.
        INCLUDE STRUCTURE VEDPN.
DATA: END   OF TKOMSERVPN.
DATA: BEGIN OF TKOMSER OCCURS 5.
        INCLUDE STRUCTURE RISERLS.
DATA: END   OF TKOMSER.
DATA: BEGIN OF TKOMSER_PRINT OCCURS 5.
        INCLUDE STRUCTURE KOMSER.
DATA: END   OF TKOMSER_PRINT.
DATA: BEGIN OF TFPLTDR OCCURS 5.
        INCLUDE STRUCTURE FPLTDR.
DATA: END   OF TFPLTDR.
DATA: TADDI_PRINT TYPE ADDI_SO_PRINT_ITAB WITH HEADER LINE.
TYPES:BEGIN OF ty_orders ,
     xblnr    LIKE mkpf-xblnr,       "delivery number
     erfmg    LIKE mseg-erfmg,       "goods issue quantity
     custname LIKE kna1-name1,       "customer name
     bstnk    LIKE vbak-bstnk,       "purchase order number
     ean11    LIKE vbap-ean11,       "upc
     kdmat    LIKE vbap-kdmat,       "customer material code
     arktx    LIKE vbap-arktx,       "description
     csrno    LIKE kna1-kunnr,       "customer service rep number
     spras    LIKE kna1-spras,       "customer language key
     csrname LIKE kna1-name1,       "customer service rep name
     csremail LIKE adr6-smtp_addr,   "csr email
     csrphone LIKE kna1-telf1,       "csr telephone
     csrext   LIKE adrc-tel_extens, "csr extension
     csrfax   LIKE kna1-telfx,       "csr fax
     total    LIKE lips-lfimg,       "cut quantity
     ldate(18)    TYPE c,
   END OF ty_orders.
CONSTANTS: c_kschl_order LIKE nast-kschl
                         VALUE 'ZUS0',
            c_kschl_order1 LIKE nast-kschl
                         VALUE 'ZUS1',            c_parvw_shipto LIKE vbpa-parvw
                         VALUE 'WE',
            c_parvw_csr    LIKE vbpa-parvw
                         VALUE 'ZS',
             c_eng(1)       TYPE c VALUE 'E',
             c_sep(1)       TYPE c VALUE '/',
             c_sale(25) type c VALUE 'Sales Order'.
DATA: WA_VBAK TYPE VBAK,
      tbl_ord TYPE ty_orders OCCURS 0 WITH HEADER LINE,
      w_csrname(30) TYPE c,
     w_csrno(30)    TYPE c,
     w_email    LIKE adr6-smtp_addr,
     f_shipto_found     TYPE c,
     w_custname(30) TYPE c,
     w_month(2),
     w_ldate(18),
     w_total LIKE lips-lfimg,
     w_lines        TYPE i VALUE 0,
     f_mail(1) TYPE c,
     cnt_1          TYPE i VALUE 0,
     cnt_2          TYPE i VALUE 0,
     tbl_otf     LIKE itcoo OCCURS 0 WITH HEADER LINE,
     w_type(25)     TYPE c,
     st_doc_data   LIKE sodocchgi1,
     tbl_objtxt    LIKE solisti1 OCCURS 10 WITH HEADER LINE,
     tbl_line      LIKE tline OCCURS 0 WITH HEADER LINE,
     tbl_attach    LIKE solisti1 OCCURS 10 WITH HEADER LINE,
     tbl_objhead   LIKE solisti1 OCCURS 10 WITH HEADER LINE,
     tbl_proc_para LIKE soparai1 OCCURS 10 WITH HEADER LINE,
     tbl_maillist LIKE somlreci1 OCCURS 10 WITH HEADER LINE,
     tbl_pack_list LIKE sopcklsti1 OCCURS 10 WITH HEADER LINE,
     tbl_cpo      LIKE itcpo OCCURS 0 WITH HEADER LINE,"SAPscript output
                                                            " interface
     tbl_cpp LIKE itcpp OCCURS 0 WITH HEADER LINE,"SAPscript output
                                                   " parameters
     tbl_smtp TYPE szadr_adsmtp_line OCCURS 0 WITH HEADER LINE,
     tbl_cdhdpos LIKE cdshw OCCURS 0 WITH HEADER LINE,
     tbl_cdpos LIKE cdshw OCCURS 0 WITH HEADER LINE,
     wrk_lines LIKE sy-tabix,
     hltlines   TYPE i,
     off1       TYPE p,
     fle1(2)    TYPE p,
     fle2(2)    TYPE p,
     htabix     LIKE sy-tabix,
     hfeld(500) TYPE c.
FORM ENTRY USING RETURN_CODE US_SCREEN.
if sy-tcode = 'VA01'.
IF nast-kschl = c_kschl_order.
SELECT SINGLE * FROM VBAK INTO WA_VBAK WHERE vbeln = nast-objky.
IF SY-SUBRC = 0.
CLEAR RETCODE.
XSCREEN = US_SCREEN.
PERFORM PROCESSING USING us_screen.
IF RETCODE NE 0.
    RETURN_CODE = 1.
ELSE.
    RETURN_CODE = 0.
ENDIF.
   ELSE.
      retcode = sy-subrc.
      syst-msgid = 'ZVERROR'.
      syst-msgno = '000'.
      syst-msgty = 'E'.
      syst-msgv1 = NAST-KSCHL.
     syst-msgv1 = 'Sales Order cut letter
                   for this order already issued'.
     syst-msgv2 = ' '.
      PERFORM protocol_update.
    ENDIF.
ELSE.
    CLEAR retcode.
    xscreen = us_screen.
    PERFORM processing USING us_screen.
    IF retcode NE 0.
      return_code = 1.
    ELSE.
      return_code = 0.
    ENDIF.
ENDIF.
endif.
ENDFORM.
      FORM PROCESSING                                               *
FORM PROCESSING USING proc_screen.
CASE nast-kschl.
    WHEN c_kschl_order.
      PERFORM get_orders.
      CHECK retcode = 0.
      PERFORM openform USING proc_screen vbak-landtx.
      CHECK retcode = 0.
      PERFORM layout.
      CHECK retcode = 0.
      CHECK proc_screen NE 'X'.
      w_type = c_sale.
      PERFORM send_email USING proc_screen.
WHEN c_kschl_order1.
     PERFORM get_orders.
     CHECK retcode = 0.
     CHECK proc_screen NE 'X'.
     w_type = c_sale.
     PERFORM send_email USING proc_screen.
   WHEN OTHERS.
      retcode = 1.
      syst-msgid = 'E0'.
      syst-msgno = '430'.
      syst-msgty = 'E'.
      PERFORM protocol_update.
ENDCASE.
IF retcode EQ 0.
    syst-msgid = '69'.
    syst-msgno = '254'.
    syst-msgty = 'S'.
    syst-msgv1 = nast-kschl.
    PERFORM protocol_update.
ELSE.
    syst-msgid = 'CKCC'.
    syst-msgno = '036'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.
      FORM PROTOCOL_UPDATE                                          *
      The messages are collected for the processing protocol.       *
FORM PROTOCOL_UPDATE.
IF xscreen EQ space.
    CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
       EXPORTING
            MSG_ARBGB = SYST-MSGID
            MSG_NR    = SYST-MSGNO
            MSG_TY    = SYST-MSGTY
            MSG_V1    = SYST-MSGV1
            MSG_V2    = SYST-MSGV2
            MSG_V3    = SYST-MSGV3
            MSG_V4    = SYST-MSGV4
       EXCEPTIONS
            OTHERS    = 1.
   ELSE.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   ENDIF.
ENDFORM.
*&      Form get_orders
      text
--> p1        text
<-- p2        text
FORM get_orders.
DATA : f_csr_found        TYPE c.
SELECT SINGLE vbeln vkorg vdatu bstnk kunnr
    FROM   vbak
    INTO (vbak-vbeln,vbak-vkorg,vbak-vdatu,vbak-bstnk,vbak-kunnr)
    WHERE vbeln EQ nast-objky.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'VN'.
    syst-msgno = '203'.
    syst-msgty = 'E'.
    syst-msgv1 = 'VBAK'.
    syst-msgv2 = sy-subrc.
    PERFORM protocol_update.
ENDIF.
SELECT vbeln posnr matnr pmatn arktx abgru kdmat werks
FROM vbap
INTO (vbap-vbeln,vbap-posnr,vbap-matnr,vbap-pmatn,
vbap-arktx,vbap-abgru,vbap-kdmat,vbap-werks)
WHERE vbeln = vbak-vbeln
AND abgru NE space "select items havng Rejection Reason
and PSTYV NE 'ZHDR'.
to check whether the reason for rejection was picked from the
managed codes tables
data: war_abgru type abgru,
      w_exist type c.
clear : war_abgru, w_exist.
select single abgru from ZMAT_REJ002
                into war_abgru
                where vkorg = vbak-vkorg
                and kunnr <> vbak-kunnr
                and MATNR = vbap-matnr
                and datef <= vbak-vdatu
                and datet >= vbak-vdatu.
   if sy-subrc <> 0.
         select single abgru from ZMAT_REJ003
                          into war_abgru
                          where vkorg = vbak-vkorg
                          and kunnr <> vbak-kunnr
                          and MATNR = vbap-matnr
                          and datef <= vbak-vdatu
                          and datet >= vbak-vdatu.
         if sy-subrc <> 0.
                select single abgru from ZMAT_REJ001
                          into war_abgru
                          where vkorg = vbak-vkorg
                          and werks <> vbap-werks
                          and matnr = vbap-matnr
                          and datef <= vbak-vdatu
                          and datet >= vbak-vdatu.
                if sy-subrc <> 0.
                     select single abgru from ZMAT_REJ004
                                         into war_abgru
                                         where vkorg = vbak-vkorg
                                         and matnr = vbap-matnr
                                         and datef >= vbak-vdatu
                                         and datet <= vbak-vdatu.
                     if sy-subrc <> 0.
                     else.
                     w_exist = 'X'.
                     endif.
               else.
               w_exist = 'X'.
               endif.
         else.
         w_exist = 'X'.
         endif.
   else.
   w_exist = 'X'.
   endif.
if w_exist = 'X'.
end for check from managed codes table
*to find the quantity fields
    SELECT SINGLE wmeng bmeng
    FROM vbep
    INTO (vbep-wmeng,vbep-bmeng)
    WHERE vbeln EQ vbap-vbeln
    AND   posnr EQ vbap-posnr.
*to get info about the customer
    SELECT SINGLE kunnr
    FROM vbpa
    INTO vbpa-kunnr
    WHERE vbeln EQ vbak-vbeln
    AND    parvw EQ c_parvw_shipto.
     IF sy-subrc EQ 0.
      f_shipto_found = 'X'.
      SELECT SINGLE name1 spras
        FROM kna1
        INTO (kna1-name1,kna1-spras)
        WHERE kunnr EQ vbpa-kunnr.
      IF sy-subrc EQ 0.
        w_custname = kna1-name1.
        CLEAR kna1-name1.
      ENDIF.
     ENDIF.
     SELECT SINGLE kunnr
    FROM vbpa
    INTO vbpa-kunnr
    WHERE vbeln EQ vbak-vbeln
    AND   parvw EQ c_parvw_csr.
    IF SY-SUBRC EQ 0.
     f_csr_found = 'X'.
      SELECT SINGLE kunnr name1 name2 adrnr
       FROM kna1
       INTO (kna1-kunnr,kna1-name1,kna1-name2,
             kna1-adrnr)
       WHERE kunnr EQ vbpa-kunnr.
      IF sy-subrc EQ 0.
        w_csrno = kna1-kunnr.
        w_csrname = kna1-name1.
        CLEAR kna1-name1.
           SELECT SINGLE tel_number tel_extens fax_number
             FROM adrc
             INTO (adrc-tel_number,adrc-tel_extens,
   adrc-fax_number)
             WHERE addrnumber EQ kna1-adrnr.
        CLEAR: adr6, w_email.
        SELECT SINGLE * FROM adr6 WHERE addrnumber = kna1-adrnr.
        IF sy-subrc = 0.
          w_email = adr6-smtp_addr.
        ENDIF.
      ENDIF.
    ENDIF.
*to get the date format in french
    IF kna1-spras NE c_eng.
      w_month = sy-datum+4(2).
      SELECT SINGLE ltx
        FROM t247
        INTO t247-ltx
        WHERE spras EQ kna1-spras
        AND mnr EQ w_month.
      CONCATENATE sy-datum+6(2)
                  t247-ltx
                  sy-datum+0(4)
                  INTO w_ldate
                  SEPARATED BY space.
      ELSE.
      CONCATENATE sy-datum+4(2)
                  sy-datum+6(2)
                  sy-datum+0(4)
                  INTO w_ldate
                  SEPARATED BY c_sep.
    ENDIF.
    w_total = vbep-wmeng - vbep-bmeng.
     IF w_total GT 0.
     PERFORM fill_orders.
    ELSE.
      IF vbap-abgru NE space.
        w_total = vbep-wmeng.
        PERFORM fill_orders.
      ENDIF.
    ENDIF.
    CLEAR vbap.
    endif.           " check for w_exist for Managed Codes entry
ENDSELECT.
IF tbl_ord[] IS INITIAL.
    retcode = 1.
    syst-msgid = 'FZ'.
    syst-msgno = '027'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
IF f_csr_found IS INITIAL.
    syst-msgid = '8B'.
    syst-msgno = '127'.
    syst-msgty = 'W'.
    syst-msgv1 = c_parvw_csr.
    PERFORM protocol_update.
ENDIF.
IF f_shipto_found IS INITIAL.
    syst-msgid = '8B'.
    syst-msgno = '127'.
    syst-msgty = 'W'.
    syst-msgv1 = c_parvw_shipto.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " get_orders
*&      Form layout
      text
--> p1        text
<-- p2        text
FORM layout.
SORT tbl_ord BY bstnk kdmat.
LOOP AT tbl_ord.
    AT FIRST.
      PERFORM writeform_text.
    ENDAT.
    PERFORM writeform.
    AT LAST.
      PERFORM writeform_footer.
    ENDAT.
ENDLOOP.
CLEAR : cnt_1,cnt_2.
PERFORM closeform.
ENDFORM.                    " layout
*&      Form openform
      text
FORM openform USING us_screen us_country.
DESCRIBE TABLE tbl_ord LINES w_lines.
IF w_lines EQ 0.
    retcode    = '1'.
    syst-msgid = 'FE'.
    syst-msgno = '078'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
CHECK retcode EQ 0.
INCLUDE zrvadopfo.
ENDFORM.                    " openform
*&      Form send_email
      text
     -->P_PROC_SCREEN text
FORM send_email USING    PROC_SCREEN.
f_mail = 'X'.
PERFORM openform USING proc_screen vbak-landtx.
LOOP AT tbl_ord.
    AT FIRST.
      PERFORM writeform_text.
    ENDAT.
    PERFORM writeform.
    AT LAST.
      PERFORM writeform_footer.
    ENDAT.
ENDLOOP.
CLEAR cnt_2.
PERFORM closeform.
CALL FUNCTION 'CONVERT_OTF'
       EXPORTING
            format                = 'PDF' "'ASCII'
       IMPORTING
            bin_filesize          = st_doc_data-doc_size
       TABLES
            otf                   = tbl_otf
            lines                 = tbl_line
       EXCEPTIONS                                           "DEVK912166
            err_max_linewidth     = 1
            err_format            = 2
            err_conv_not_possible = 3
            OTHERS                = 4.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'OA'.                                      "DEVK912166
    syst-msgno = '186'.                                     "DEVK912166
    syst-msgty = 'E'.                                       "DEVK912166
    PERFORM protocol_update.
ENDIF.
REFRESH tbl_objtxt.
CLEAR tbl_objtxt.
CLEAR tbl_proc_para.
REFRESH tbl_proc_para.
CLEAR tbl_maillist.
REFRESH tbl_maillist.
CLEAR tbl_pack_list.
REFRESH tbl_pack_list.
st_doc_data-obj_name   = 'Sales Order Cut Letter'.
st_doc_data-obj_langu   = 'E'.                            "DEVK905849
st_doc_data-sensitivty = 'F'.                            "DEVK905849
st_doc_data-obj_prio    = 1.                             "DEVK905849
CONCATENATE w_type 'Cut Letter' INTO          "#EC NOTEXT
                              st_doc_data-obj_descr SEPARATED BY space.
DATA w_line(3) TYPE c.
PERFORM format_pdf.                                       "DEVK905849
concatenate VBAK-VBELN '.PDF' into tbl_objhead.
tbl_objhead = 'Sales Order Cut Letter.PDF'.
APPEND tbl_objhead.
       "DEVK905849
CLEAR wrk_lines.
DESCRIBE TABLE tbl_attach LINES wrk_lines.
fields needed for email
tbl_maillist-com_type = 'INT'.
tbl_maillist-receiver = w_email.
tbl_maillist-rec_type = 'U'.
APPEND tbl_maillist.
send email
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                                  STARTING NEW TASK 'MAIL'
       EXPORTING
            document_data              = st_doc_data
            document_type              = 'PDF'
            COMMIT_WORK                = 'X'    " added after ECC6.0 upgrade
       TABLES
            object_header              = tbl_objhead
            object_content             = tbl_objtxt
            receivers                  = tbl_maillist
       EXCEPTIONS                                           "DEVK912166
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            OTHERS                     = 8
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'ZA_G'.                                    "DEVK912166
    syst-msgno = '922'.                                     "DEVK912166
    syst-msgty = 'E'.                                       "DEVK912166
    syst-msgv1 = sy-subrc.                                  "DEVK912166
    syst-msgv2 = tbl_smtp-adsmtp-smtp_addr.                 "DEVK912166
    PERFORM protocol_update.
    syst-msgid = 'VW'.
    syst-msgno = '001'.
    syst-msgty = 'E'.
    syst-msgv1 = 'Print successful:email Recepient Invalid'."#EC NOTEXT
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " send_email
*&      Form fill_orders
      text
--> p1        text
<-- p2        text
FORM fill_orders.
tbl_ord-bstnk    = vbak-bstnk.
tbl_ord-kdmat    = vbap-kdmat.
tbl_ord-xblnr    = vbak-vbeln.
tbl_ord-ean11    = vbap-pmatn.
tbl_ord-arktx    = vbap-arktx.
tbl_ord-csrno    = w_csrno .
tbl_ord-csremail = w_email.
tbl_ord-spras    = kna1-spras .
tbl_ord-csrphone = adrc-tel_number.
tbl_ord-csrfax   = adrc-fax_number.
tbl_ord-csrext   = adrc-tel_extens.
tbl_ord-total    = w_total.
tbl_ord-custname = w_custname.
tbl_ord-csrname = w_csrname .
tbl_ord-ldate    = w_ldate.
APPEND tbl_ord.
CLEAR tbl_ord.
CLEAR w_total.
CLEAR w_ldate.
ENDFORM.                    " fill_orders
*&      Form writeform_text
      text
--> p1        text
<-- p2        text
FORM writeform_text.
CALL FUNCTION 'WRITE_FORM'
       EXPORTING
            element = 'WTEXT'
            window = 'WINDOW2'
       EXCEPTIONS
            element = 1
            window = 2.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'EBR'.
    syst-msgno = '056'.
    syst-msgty = 'E'.
    syst-msgv1 = 'WTEXT'.
    syst-msgv2 = 'WINDOW2'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " writeform_text
*&      Form writeform
      text
--> p1        text
<-- p2        text
FORM writeform.
CALL FUNCTION 'WRITE_FORM'
       EXPORTING
            element = 'EMAIN'
            window = 'MAIN'
       EXCEPTIONS
            element = 1
            window = 2.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'EBR'.
    syst-msgno = '056'.
    syst-msgty = 'E'.
    syst-msgv1 = 'WTEXT'.
    syst-msgv2 = 'WINDOW2'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " writeform
*&      Form writeform_footer
      text
--> p1        text
<-- p2        text
FORM writeform_footer.
IF nast-spras = 'N'.
    CALL FUNCTION 'WRITE_FORM'
         EXPORTING
              element = 'FOOTER'
              window = 'MAIN'
         EXCEPTIONS
              element = 1
              window = 2.
ENDIF.
CALL FUNCTION 'WRITE_FORM'
       EXPORTING
            element = 'WFOOTER'
            window = 'WINDOW12'
       EXCEPTIONS
            element = 1
            window = 2.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'EBR'.
    syst-msgno = '056'.
    syst-msgty = 'E'.
    syst-msgv1 = 'WFOOTER'.
    syst-msgv2 = 'WINDOW12'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " writeform_footer
*&      Form closeform
      text
--> p1        text
<-- p2        text
FORM closeform.
CALL FUNCTION 'CLOSE_FORM'
       TABLES
            otfdata                  = tbl_otf
       EXCEPTIONS
            unopened                 = 1
            bad_pageformat_for_print = 2
            OTHERS                   = 3.
IF sy-subrc NE 0.
    retcode = sy-subrc.
    syst-msgid = 'PS'.
    syst-msgno = '005'.
    syst-msgty = 'E'.
    PERFORM protocol_update.
ENDIF.
ENDFORM.                    " closeform
*&      Form format_pdf
      text
--> p1        text
<-- p2        text
FORM format_pdf.
FIELD-SYMBOLS <fs>.
DESCRIBE TABLE tbl_line    LINES hltlines.
DESCRIBE FIELD tbl_line    LENGTH fle1 IN BYTE MODE . Defect#1579-
DESCRIBE FIELD tbl_objtxt LENGTH fle2 IN BYTE MODE . Defect#1579-
Start of Defect#1579+
DESCRIBE FIELD tbl_line    LENGTH fle1 IN CHARACTER MODE.
DESCRIBE FIELD tbl_objtxt LENGTH fle2 IN CHARACTER MODE.
End of Defect#1579+
CLEAR   tbl_objtxt.
REFRESH tbl_objtxt.
LOOP AT tbl_line.
    htabix = sy-tabix.
    MOVE tbl_line TO hfeld+off1.
    IF htabix = hltlines.
      fle1 = strlen( tbl_line ).
    ENDIF.
    off1 = off1 + fle1.
    IF off1 GE fle2.
      CLEAR tbl_objtxt.
      tbl_objtxt = hfeld(fle2).
      APPEND tbl_objtxt.
      SHIFT hfeld BY fle2 PLACES.
      off1 = off1 - fle2.
    ENDIF.
    IF htabix = hltlines.
      IF off1 GT 0.
        CLEAR tbl_objtxt.
        tbl_objtxt = hfeld(off1).
        APPEND tbl_objtxt.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDFORM.                    " format_pdf
ANy Suggestion or help will be appreciated!
Regards,
Kittu
Edited by: Kittu on Jun 30, 2008 12:32 PM

Hello Julie Waller,
Very Good evening!
Thank you very much for your response!
Sometimes...I miss the basic things and start concentarcting on typical ways to fix the issue. ....which will only make my issue critical.
Hello Sathya,
Thank you for your response!
POints are rewarded..
Have a great day ahead!
Regards,
Kittu

Out Put Type for Delivery

Hi friends
I would request you to guide me to assign output type to delivery .
Regards
jp

Hi there,
You do all the O/p procedures in SPRO -> Logistics Execution --> Shipping --> Basic functions --> O/p control.
There 1st define a new O/p type. In the transmission medium mention if it is a prinout or EDI or external send (mail). In the default values mention if it is to trigger immediately or upon running of a batch job.
Then define & assign an O/p control prog in which you mention how the O/p is supposed to trigger, smart forms for the form layout etc.
Define the access sequence & assign it to the O/p type.
Maintain the O/p determination procedures. Assign the O/p type to the procedures. In the requirement routine put a condition as to when the O/p is to be triggered if required. For eg if it has to triggr immediately after saving the delivery or upon PGI.
Then assign the O/p determination procedure to the delivery types.
Fianlly maintain the condition records sotht it will trigger the O/p based on the requirement. Also if it is a print O/p, in communication assign a printer name (local or any other name) sothat the printout will come from that printer.
Refer http://help.sap.com/erp2005_ehp_03/helpdata/EN/30/c6853488601e33e10000009b38f83b/frameset.htm
for further information on O/p determination.
Regards,
Sivanand

Output type for non assigment Handling Unit

Hi All.
I would like to make a Output type for non assigned Handling Unit
Can anyone tell me about it?
Edited by: John Brown on Feb 9, 2010 10:53 AM

Make a new output type, transaction NACE, application V6 (Handling unit) and assign the output type to your output procedure.
Create a new output requirement, transaction VOFM and assign it to the output type in the output procedure. In the requirement check on KOMKBV6-VPOBJ. The value of KOMKBV6-VPOBJ shows to which object the handling unit is assigned: '00' or empty for not assigned, '01' for outbound delivery. See the domain VPOBJ for all possible values.
Reagards Jack

Output Type for VL02N

Dear Experts,
I have created a output type for the application V2.
our requirment is when a user goto transaction VL02N click on Outbound Delivery->Issue Delevery Output then the Output Type should be displayed and if he clicks on that Output Type the script should execute.
my question is after we create Output type is anything else to do to get that Output Type in specific transaction?
thnx in advance...
V

Hi,
As per your question, I assume you are asking for getting a pop-up window for selecting the Output types when executing the ISSUE OUTPUT transaction in VL02N.
If you configured the Output type and maintain necessary setting in Output Determination procedure and Condition records.,& assignment of Smartforms and Print programs, then as per standard
A pop-up will appear with the Output type and the Processing status of it, there you will have options
1. To print
2. To Print preview
3. To check Print options.
This is the standard design, Please check with the Developer if this design was modified in the Print program .
Please revert back if you need more details.
regards,
santosh

Output type for IDOC creation

Hi Sapgurus,
Can anybody help as per below.
Client has third party interface system from which they access stock data from SAP system to front end system.They required stock quantity.As per below transaction I have to create output type for IDOC creation for below t codes.Pls guide for creating output type.
Note: Consider as per MM point of view.Output type is not for printout,It is for IDOC to display stock at front end system.
MB1C u2013 Inward + Outward (As per movement types)
MB1B u2013 Inward + Outward (As per movement types)
VL02N - Inward + Outward (As per Delivery types (Inbound & Outbound))
VL06G - Outward
VL09 - Inward + Outward (As per Delivery types (Inbound & Outbound)
MB0A u2013 Inward
MB01 u2013 Inward
MBST u2013 Reversal of Inward stock

Hi,,
Check the below idoc WMIVID01
"IDoc for Inventory"" in help.sap.com
regards,
Lalita

Qulaity Certificate "Output Type " for delivery

Similar Messages

Maybe you are looking for