Issue delivery output

Dear Gurus...
On the VL02N initial screen, After I write outbound delivery number, I want to get print-out without entering the VL02N screen. So I follow the path as Outbound delivery> Issue delivery output and system shows only ONE output OPTION as "Z040"
But to fix this issue I enter the VL02N screen and follow the path as:
Extras>Delivery output>Header>I choose output type which "Z030 AND Z040" After I choose these types, then I am able to get outputs..
I want to get outputs from initial VL02N screen..
So how can I accoplish this???
thansk in advance....

Hi,
As I understood from your requirement, you want to print 2 output types from the initial VL02N screen. (Z030 AND Z040) But as at now when you go to VL02N, you can see only Z040. Therefore you have to go in to VL02N and add Z030 every time to get that printout.
So now what you want is to get those 2 outputs attached automatically; so that you can get print outs from the initial screen of VL02N.
You can do this.
Go to VV21 transaction.
Select your output type. (Z030) and press enter key
If there is any access sequence select relevant one.
Enter relevant data
Under "Communication" button maintain relevant output device as well. (If your not too sure as what to maintain go to VV22 transaction for your correct output (Z040) and do same for Z030 as well
Save it.
Then create a new delivery and see the output option from the initial screen of VL02N.
You should be able to see both Z030 AND Z040.
Try and revert.
Best regards,
Anupa

Similar Messages

Why can't I use the function of menu item 'issue delivery output'?

why can't I use the function of menu item 'issue delivery output' in main screen of delivery note?
And at the same time I can't use the button of printing in main screen of delivery note.
the main screen of delivery note I mean above is in screen of maintaining shipping data instand of the first screen of VL02N.
TKS in advance.

Hi,
Because delivery will be having header level output and item level output. So if u try to print through main screen then system will not know whether it is header related or item related. That is the reason it is only print output at header level or item level but not in main screen.
I think u may have doubt like how billin will be issued output through Main screen. Because for billing both header and item level data are same..
Regards
Sankar

Assigning custom form to delivery output

Hi Experts,
I have developed a custom smart form and I need to attache the same to delivery out put.
Here my question is, How should i read delivery number entered in 'issue delivery output' and pass the same to my custom form.
Based on this it will fetch the data...
Appreciate your help.
Thanks in advance.
Indra

Hi,
You have to add the Output type in the Header-Output of the delivery.
Go to NACE transaction-Select Application V2 - Select output type - Go to Processing routines- Give the Print Program, Entry point in the program (desired sub routine ) and then Smartform to print it.
Generally, Functional Consultants set these.
You can take their help.
KC

Outbound delivery output not re-determined during goods issue?

Hi,
i'm currently in the process of testing an SAP upgrade from 4.6B to ECC 6.0, and have encountered the following problem: one of our outbound delivery output types (LD00) is supposed to print out at goods issue (which happens in VT02N, by the shipment).
In 4.6B, the output determination procedure correctly triggers at goods issue, however, in 6.0, it doesn't. Re-opening the delivery in VT02n causes the LD00 to be determined after all, but by then it's too late.
Does anyone have the slightest idea why the output determination isn't re-evalutated at goods issue?
regards
Rob

Hi,
Perhaps you are using an own VOFM subroutine to do filters if the output works or no. You create this subroutine with tcode VOFM, and after some steps you create an include in a report of SAP (SAPL). You can check if you are setting a VOFM in SM34/VVC_T683_XX_E1 for the output scheme. Sometimes is necesary to run this report to create and activate the report sapl, if no, when the abap call the subrutine, SAP doesn't find (perform * if found)
For VOFM there is a good document in google, format PDF, search it with the string inside vofm ext:pdf.
I hope this helps you
Regards,
Eduardo

New address to be printed in the delivery output type

Dear all,
For the delivery i issued one output message to take the printout of the shipping label .
Now i changed the address in the ship to party and again issued the message , still it is taking the old adress only is there any possibility for the new address to be reflected in the output message with out creating the new deelivery numbe .
Best Regards,
Kumar

Hi there,
In the O/p type form layout, in the ship-to address field mapping check what mapping is done. If the mapping is done to LIKP-KUNNR, then if you change the ship-to address, then the new address will come into the print out if you retrigger the O/p.
If the mapping is done to pick it from VBPA tables of the relevant sales order, then it willnot update.
So check the field mapping in the printout.
Regards,
Sivanand

Delivery output after PGI

Hi,
I have a scenario in which user is asking us to make the changes to the delivery output control for a particular customer
in way that the delivery note is printed only after the PGI is done.Can any one help me to slove this issue.
Regards
Ram Pedarla
Edited by: aram ust on May 9, 2008 1:52 PM

In your output access sequence, put a requirement on it.
Requirement 001, (include LV61B001) limits to only when goods issued. If you need to be specific to a customer then copy this to your own defined requirement (600 -999) in VOFM.

New Custom Field in Delivery output Communication Structure

Hello friends,
I need your help to Solve my below problem
We want the delivery output to be triggered based on the shipping point and storage location.
Storage location is at item level and is not in LIKP and hence not in KOMKBV2 (Output Comm Structure for Deliveries)
I have created a new Field ZZLGORT in the Header Strucutre and has performed thefolloiwng steps
1. Include field ZZLGORT in communication structure KOMKBV2. This is an Include that is provided for additional fields.
Add the field with the name ZZLGORT in Include KOMKBZ4.
2. In structure KOMB in Include KOMBZ, have added the same field
(same procedure as for item 1).
3. In view V_T681F, I created the same field with transaction SM31 under key B V2.
4. Program LVCOMU04 contains Perform USEREXIT_KOMKBV2_FILL. This Perform
is in program RVCOMFZZ.
Modiied the source code as follows:
FORM_USEREXIT_KOMKBV2_FILL.
COM_KBV2-ZZLGORT = item Storage location.
When i am in Debugging mode till the last minute the structure COM_KBV2-ZZLGORT is having the storage location value.
so there is no problem in the userexit logic.
5) I have created a new cond table , and assigned the table access sequence and assigned he access seq to the Delivery output type
When i created the Delivery , the output analysis screen shows that the field ZZLGORT is blank ( With exclamation Mark) and it says Access Not made (initialized Field )
can any one of you tell me what is the step i am missing out to make sure that the analysis screen has the storage location.
and also the system reading the condition record and issuing the output.
i have checked whether the output is issued by some other condition or not. no there is only condition record and its triggering that condition record but the analysis shows "Output Not found"
Can any one of you help me here please. Your immediate inputs will be of great help to me
Thanks & Regards
Srini

Hi Srini,
As per note 32662 it seems you have followed all the steps, but might be that you didn't do in proper sequence.
The note states that:
"If a new access sequence and condition table was created before the communication structure was modified, it must be deleted again. Items 1 to 5 must be carried out in the specified sequence."
So I guess the key for you would be to delete the Condition table and access and create them again.
Regards,
Ganesh

How to print the changed address in delivery output

Dear Gurus,
As all we know the customer address comes in sales order from customer master table or address table and further get copied into delivery also in case of same SP and SH.
My issue is that we do not maintain different SH for a sold to party so SP = SH and there addresses will also be same.
In output we are getting address from ADRC table.
Now if we change the ship to party address in delivery manually and get the output the printed address is unchanged.
But I want to print the changed address in delivery output without changing the masters and maintaining diiferent ship to party.
Please help me how to determine it in print out???
Thanks,
Sanjay

Hi,
I think the logic you have written is wrongly on output.
The logic is like this:
Pass the document number into "VBPA" table.
Execute.
Fetch the address number against "WE(ship-to-party)".
Pass the same address number into "ADRC" table to get the address.
Here you will get the new address which is different from the maaster data.
Regards,
Krishna.

Delivery Output

Hi Everybody,
We have a delivery output type ZASN. The output type has a requirement 1 assigned in the output determination procedure. The requirement is to make the output get determined only after the PGI has been done. We have all our Picking and PGIs done through EDI. When we do the PGI through EDI, the output ZASN does not get determined in the delivery. Surprisingly, when I do the PGI manually using VL02N, I see the output getting issued. Also for the deliveries for which the PGI was done by EDI and no output was issued, I can just go onto VL02N, five the delivery number, hit enter and just come out and my output gets triggered. Strange behaviour though.
Has anybody encountered this situation? I tried looking for an OSS note but couldnt find anything relevant. Any help would be appreciated.
Thanks & Regards,
Vidya

Hi,
I also encontered with this situation but in my situation i was creating the outboubd del and pick/pgi also through the edi and this was one after another so what we did is triggered the output type on creation ( before pgi ) . As both processes were at one time it doesnot make any difference to trigger the o/p on creation of del .But this is standard sap issue of not triigering the o/p message on pgi through the edi.

Pro forma invoice from a Delivery Output using "8 - Special Function"

SAP Gurus
I am interested to create a proforma invoice for a delivery that is created in the system using VL01N. I am using an option to use the Delivery output to be allow creation of the pro forma invoice. I created a new output type and assigned 8 - Special function as the medium of the output.
I managed to find a BAPI that serves this purpose perfectly. Please look at BAPI_BILLINGDOC_CREATEFROMDATA. Enter the following Parameters.
In table BILLINGDATAIN insert one line with the following data:
ORDBILLTYP = ZFDP
REF_DOC = Delivery number
REF_DOC_CA = 'J'
The BAPI when it runs on own, creates the required pro forma invoice. But when it is attached to the output type to be triggered as a special function, does not work. What kind of routine should I enter in the processing routine.
Program on output screen is ZFDP_BAPI
Form Routine is ENTRY
there is a routine maintained inside the program ZFDP_BAPI called "ENTRY"
Inside the subroutine ENTRY, the BAPI_BILLINGDOC_CREATEFROMDATA is invoked.
Please advice.
Thank you.

Hello
Thanks for the reply. Earlier when I was using the BAPI BAPI_BILLINGDOC_CREATEFROMDATA, The BAPI used for the output type did not work as it uses u2018Commit Worku2019 statement and it interferes with the u2018commitu2019 of standard program. Due to this reason the transaction dumps every time.
Are you performing the output with dispatch time '4' ? - the answer is yes, I am.
Just double -checking with you that if you decide to use Use BAPI BAPI_BILLINGDOC_CREATEMULTIPLE and call it in background task, do you think that the we can get past this issue short dump issue?
Thanks

Blocking delivery output types

Hi All,
I am doing my coding in user exit MV50AFZ1 for checking transportation data for the line items in STO. If it is not maintained then we should block that delivery. For that we are changing likp-lifsk and xlikp-lifsk value to 01(Block). Now client has added some new functionality to this. Now he is able to issue the delivery output with output types. We should be able BLOCK this also. Any pointers to do this will be of great help. We tried changing value lips-kvgr1 and xlips-kvgr1 to NDO, But it is not working.
Regards,
Vinod.

Hi,
Create a VOFM requirements routine for the output..And then assign that VOFm routine to the output type in the output determination procedure..
In that VOFM routine have the following code..
SY-SUBRC = 0. " Propose the output type.
IF XLIKP-LIFSK = '01'. " Don't propose the output type if the delivery block is set.
SY-SUBRC = 4.
ENDIF.
***If XLIKP-LIFSK is not available then try using
KOMKBV2-LIFSK.
Thanks
Naren

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

Issuing two outputs at a time.

For a given invoice,we have to issue ouput(Smartform) to Bill-to-party with BP Address.
Also we need to check the buying group(KNB1-EKVBD) of sold-to-party with that of Bill-to-party. If the buying group of SP and BP is different,then we need to issue output also to Payer with PY Address(instead of BP Address).So in this case we need to issue two outputs : one for SP and another for PY with different addresses.
How can we achieve this? All suggestions are welcome.

Hi Nikhil,
You will need some steps. First create an additional output type with exactly the same settings as RD00.
This output type should have a requirement that should only be processed in case the buying group differs.
Then in the smartform you should copy the address-node and both adress nodes should have a Condition: one to be processed in case of output type RD00 (regular invoice) and one with the condition to be processed in case of your newly defined output type.
Regards,
John.

Consignment issues,delivery,return.plese guide customise

hi,
consignment problem and customise.

Hi,
The consignment process in SAP standard consist of four small processes:
Consignment fill-up (send materials to customer consignment).
Here you have a consignment fill-up order and a consignment fill-up delivery.
Consignment issue (issue materials from customer consignment to the customer).
Here you have a consignment issue order, consignment issue delivery and a consignment issue invoice. (the flow is very similar to a normal OR flow, but the materials are issued from the consignment stock instead of plant stock unrestricted).
Consignment return (return materials from customer ownership to customer consignment).
Here you have a consignment return order, consignment return delivery and a consignment return invoice. (the flow is very similar to a normal RE flow, but the materials are returned to the consignment stock instead of plant stock returns).
Consignment pickup (pickup consignment stock and move it to plant stock).
Here you have a consignment pickup order and a consignment pickup delivery.
Note that in consignment fillup and consignment pickup there are no invoices since there is no change of ownership for the materials.
How to perform a consignment order?
In consignment orders you are allowing the stock to sit in your customer location. Once he informs that he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.
It is defined in 4 steps.
1. Consignment fill up:
Sales document type is KB
Item category KBN
shedule line category E1
In this step, you are not invoicing the customer. document flow is sales order -
delivery item category. It will not be relevent for billing and pricing because you are not charging money for these goods in this step.
In schedule line category, you will set movement type 631 & set for availability check and TOR.
2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods.
Sales document: KE
Item category: KEN
shedule line category: C0 or C1
Here you are invoicing the customer(because he used the goods). you are assigning the delivery documnt and billing document to the sales document.
In item category, you are setting relevent for billing, pricing, special stock.
In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.
3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document.
Sales document type: KR
Item category: KRN
Shedule line category: D0
You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
4. Consignment Pick up:
Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing.
Assign retrun delivery to sales document type.
Sales document: KA
Item category: KAN
schedule line category: F0 & F1
Your setting item category relevent for returns. any shedule line category relevent for 632 movement type, MRP, availability check, delivery.
Now you check your plant stock. Stock will increase.
Regards,
Abhee.

Tax Calculation in delivery output

Hi,
I have created a sales order with 10 Qty and did partial delivery for 5 Qty around 2 months back. when i created the sale order the Local Tax (VAT) is 12.5% and now VAT is changed from 12.5% to 14.5% for a particular state.
To adopt these changes I have created new Material Tax Classification and New tax code. I maintained the conditions records for the same.
Now when i wanted to do delivery for the remainig qty (5 Qty), In sales order I changed the Tax classification of the material to get new VAT 14.5% and i saved the document. But it is not reflecting in the conditions tab b'se of partial delivey done. After doing delivery when i saw the output of delivery it is showing the value for 12.5% instead of 14.5% where as invoice is showing 14.5%. When i checked smartform of delivery it is taking conditions from KONV table where the VAT percentage is showing as 12.5% where as it is supposed to be 14.5%,
pls any one suggest me, how to get 14.5% value in my delivery output??
Regards,
Srikanth.P
Edited by: Srikky on Feb 25, 2010 4:35 PM

Hi,
Please check the Code to fetch the Vat % to the Delivery output, if the Delivery ouput is getting the right code from the KONV table where KNUMV= VBAK-KNUMV then it is the correct logic
Then goto the Delivery Document in change mode VL02N and Re-Trigger the Output and check the Layout. If once the Output was retriggered then automatically the New Data will be copied into the Layout.
Please check and revert back.
regards,
santosh

Issue delivery output

Similar Messages

Maybe you are looking for