Triggering delivery output once requirement is fullfilled

Hello,
I have created a custom output type for delivery and mentioned the custom routine in the procedure (picking complete). The issue I have now is once Picking is complete the output is not getting triggered automatically untill I go into VL02N and change something on the delivery. I tried triggering it using VL71 but its not working. How do I make it work. I want as soon as the TO is confirmed for the delivery this output to be triggered.
Thank you
Nag

Hi Nag,
Review VL10cuc and check the flag "no output determination" for profile 2000.
The flag must be clear for output determination.
Note 358634 describes in detail......
regards, david

Similar Messages

Delivery output triggered twice

Hello Dears,
When I triggered delivery output(print) thro VL02N, It printed the document twice and spools are created twice.
I can see No.of copies = 1 and in output determination analysis I see only one record was found successfully.
Can anyone suggest why does this happen?
Regards,
Nz

Probably,
1. You have configured you output type to trigger each time, there is any specific change on your doc. So, in your output type's config(NACE) General Data tab, check following things:
i). It should not be relevant for Multiple print.
ii). And there should not be any entries in change output.
or
2. 1st output type record is determined through output determination. And other is placed manually on to the doc.
Thanks, JP

Proforma Invoice triggers automatically through delivery output type

Hi Gurus,
Iam facing one issue related proforma invoice, senerios is sales order- once delievry saves, it triggers one output type ZGF8, and it triggers Proforma invoice type ZGF8.
In delievry output type ZGF8, we have output program Z_EVT_LIKP_OUTPUT, and Form Rouitne CREATE_EVENT.
Now user want to differnt delivery type and differnt proforma invoice type same as above.
My question is how the system is triggers ZGF8 proforma billing type automatically, where in the system have the setting.
Please guide
Thanks
Ramki

in creation mode you can see kew combination this will show your access sequence criteria.
Go to NACR display mode in header condition info ,click condition info tab with entering any values in screen this will show the details

Why the delivery output ASN didnt triggered??

Hi,
I configued an Output type for ASN sending, put output conditions as 'Distribution channel/Delivery Type'.
In Tcode NACE, put it into procedures 'Delivery Header Output'. put requirement 1 for it, as when 'Delivery GI posted', it will be triggered
But when i do the delivery and PGI, it didnt triggered, why???
Delivery type of the DO is correct.
Distribution Channel of the SO is meet the output conditions.
So where is the problem???
Thanks!

Hi Martina,
Thanks for your reply.
I have checked the "Dispatch Time" for the condition type in customizing. It was set as '4' which means 'Sends immediately'.
And also in actual condition record, the 'time' field are filled in '4' as the same.
So i think whether it is the access sequence cause the problem???
As the 'distribution channel' couldnt be found within the Delivery Order....??
Any other ideas??
Thanks!!!

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.

Delay triggering of Output type

I have a requirement, wherein when I do a PGI in VL02N, 2 Output Types Z1 and Z2 are triggered.
Z1 will generate the Billing Doc and Z2 will print a form with all the details inlcuding Billing Doc Number.
However, Z1 takes time (abt 30 sec) to generate Billing Document, and Z2 generates the spool simultaneously but does not display Billing Document in the form, as Z1 has not yet completed.
Is there any way, we can delay Z2 or trigger Z2 only after Z1 is completed.
Note : We don't want to use batch job.
Am new to output types, so kindly explain in detail the steps for solution.
Thanks
Vivek

Hi,
We have worked on a similar requirement. In our case we triggered the output Z2 at the time of billing. So configure Z1 during PGI in delivery and Z2 in billing. We adopted the method, you are having currently, initially. But in case of error during billing creation it was very difficult to handle the errors. The delay of 30 sec. could increase if you have huge load.
I would suggest it is logical to print only after the billing document is created so you can look at this option if you like.
Cheers,

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

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

Terminating Event Getting triggered more than once

Hi All,
I am facing a very peculiar problem in PR release workflow(item wise release, business object BUS2009).
One of the requirements of the workflow is to send a mail to PR initiator once it is rejected by any of the approvers(4, in my case). The event associated with the cancellation of the workflow is REJECTION_START.
The problem is that this event is being triggered more than once. One thing that i have observed is that if eg. second level of approver cancels it, the event is triggered twice. Likewise if third level of approver cancels it, it is being triggered thrice. Which leads to sending of 2 and 3 mails respectively to the PR initiators mailbox.
Why is this happening? Ideally, only one event should have been triggered, and the triggering of the event should have been independent of PR approver's level. I am at my wits end regarding this.
Any suggestions in this regard will be highly appreciated
Regards
Varsha Agarwal.

If you check for 2nd level rejjection two release Code is associated so it triggers 2 times and same for 3rd level approval.
I think you have to put some sort of filter using FM SAP_WAPI_WORKITEM_OBJECT
in the attribute portion of yopur custom BO.
The attribjute will check this FM and if it has entries that means already a Workflow has been triggered it should set the flag as X.
Make use of this attribute in defining the start condition of this task thru
SWB_COND.
Thanks
Arghadip

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

Delivery Output determiantion using Delivery type & Item category

Dear all,
I am facing a problem while triggering output using Delivery type/Item Category access in access sequence xyz. I have maintained the condition record for this access and did all the necessary customization settings.
When i maintain the condition record for other access in Access sequence xyz the out put is being triggered.
After some analysis i found that the Delivery type/Item category is using different communication structures.
ie. Delivery type is using KOMKBV2-LFART. where as Item Category is using KOMPBV2-PSTYV. The output is a header output.
can any one explain the problem here in maintaining different comm structures for an access for generating header output.
Thanks in advance for your inputs.
Best Regards
Satish

Hi,
You mean to say its not triggering the output automatically.....
If that is the case then goto the condition type in IMG and in tab "default values" make the dispatch time as "send immediately when saving the application" this will automatically triggers the output based on the condition records.....
Regards
Bageerath

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

Requirements not fullfilled for Condition type - Pricing Procedure

When I am doing the pricing procedure, the error thrown is "Requirements not fullfilled for Condition type". Can any one suggest how to fix this problem ?

Hi Sunil,
Please first of all check the condition type in Pricing Procedure. In condition type column check the requirement. Here conditon is, once requirement is fulfilled which you have mentioned in the condition type then only it will be executed. Take a help of ABAP'er regarding this requirement if it is customized requirement.
We should know the purpose of requirement in condition type.
Venkat.

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

Triggering delivery output once requirement is fullfilled

Similar Messages

Maybe you are looking for