Output Determination Issue

Hi All,
Pls go through below scenario.
My output type access sequence is as mentioned below.
Sales Org / Bill Type / Customer group (Email - ZC)
Sales Org / Bill Type / Customer group (Email - BP)
Sales Org / Bill Type (Print)
Routined 901 & 903 are assigned to first 2 sequences.
Purpose of routines 901 & 903:
Rountine 901 will check whether email ID is maintained against ZC partner fucntion or not. If it is maintained, then output type will be determined against ZC partner fucntion & Email will be send.
Else it will go next access sequence.
Rountine 903 will check whether email ID is maintained against BP partner fucntion or not. If it is maintained, then output type will be determined against BP partner fucntion & Email will be send.
Else
It will go for Print option.
Issue:
When I create the billing document in VF01 & go to output area , the output type is getting determined properly.
But if I don't go to output area in VF01 transaction, the output type is getting determined automatically.
Again I have to go to VF02 & save the billing document to determine the output type.
What might be the issue with scenario?
Rgds,
Senni.B

Hi All,
We found the problem.
Problem was with Routine logic.
Partner functions are checked after saving the billing document means with VBRK - VBELN & VBPA table we were written the logic where it suppose to be during run time.
Current logic is:
u2022     Select partner number of ZE partner function from dynamic run time table MSG_PART.
u2022     Pass partner number to KNVK-PARNR and select KNVK-PRSNR.
u2022     Pass KNVK-PRSNR to ADR6- PERSNUMBER and select ADR6 - SMTP_ADDR.
u2022     If ADR6 - SMTP_ADDR is not equal to null value means allow to access the condition records.
Earlier logic was:
u2022     Pass the value of VBRK u2013 VBELN to VBPA u2013 VBELN along with VBPA- PARVW = u201CZEu201D.
u2022     Pass VBPA - PARNR to KNVK-PARNR and select KNVK-PRSNR.
u2022     Pass KNVK-PRSNR to ADR6- PERSNUMBER and select ADR6 - SMTP_ADDR.
u2022     If ADR6 - SMTP_ADDR is not equal to null value means allow to access the condition records.
Thanks for your information
Rgds,
Senni.B

Similar Messages

ME38 Output determination Issue

Hi,
Issue is when ever i go to ME38 it is generation output Message and sending mail to vendor even though there is no change in schedule lines. I want to restrict this. Output should only generate when ever there is a change in Quantity. I try to set Fields relevant for Printout changes but it is not working.
Can any one help me to achieve the desired functionality...
Thanks a lot in advance....
Reddy

Hi All,
We found the problem.
Problem was with Routine logic.
Partner functions are checked after saving the billing document means with VBRK - VBELN & VBPA table we were written the logic where it suppose to be during run time.
Current logic is:
u2022     Select partner number of ZE partner function from dynamic run time table MSG_PART.
u2022     Pass partner number to KNVK-PARNR and select KNVK-PRSNR.
u2022     Pass KNVK-PRSNR to ADR6- PERSNUMBER and select ADR6 - SMTP_ADDR.
u2022     If ADR6 - SMTP_ADDR is not equal to null value means allow to access the condition records.
Earlier logic was:
u2022     Pass the value of VBRK u2013 VBELN to VBPA u2013 VBELN along with VBPA- PARVW = u201CZEu201D.
u2022     Pass VBPA - PARNR to KNVK-PARNR and select KNVK-PRSNR.
u2022     Pass KNVK-PRSNR to ADR6- PERSNUMBER and select ADR6 - SMTP_ADDR.
u2022     If ADR6 - SMTP_ADDR is not equal to null value means allow to access the condition records.
Thanks for your information
Rgds,
Senni.B

Sales Order Output determination issue

Dear expert,
I met an issue that some orders can not generate output(no output type generated). the other order under the same situation(same order type/ sales area/customer etc. ) has the output generated. I checked nearly 250 orders of last month with the same order type and sales area. more than 30 orders did not have any output generated. I use the same data in the test system several times, get the output generated every time. I can also use the VA02 to add the output manually for the 30 orders.
I already checked the related config and VV13. the related routine. they are all good seems to me.
Does any one met the same problem or can help me to analyze this issue. I am now having no direction to check...
Looking forward to your reply.
Br,
Ivan.

Ivan, you need to compare orders more properly.
for example,
-are they created by different users (if so, do users have different authorizations) ?
-have someone changed those orders later (look at Environment->Changes in VA03)?
-were those orders completed (check the logs)
did you check the printers? does the issue relate to ONE particular printer or not?
did you check that printer in SPAD ?
do you have any specific user-exits? request abaper to check some orders.
any background jobs involved?

Delivery Header Output Determination Issue

Hi all,
       I have a scenario like below.O/P condition type OPT has to be determined in Delivery header based on the Payer.
       I read the IMG-S&D-SYS.MOD-New fields for O/P Determ with Condition technique. Based on that i added the Payer Field KUNRG in KOMKBV2-Header for Communication O/P in Delivery.Since KUNRG is already in KOMB it didn't add it in the structure KOMBZ.Now i created a Condition table,Access Seq and when i assign the condition record i am not able to see all Payer in F4 of KUNRG.
       Am i missing something. Have i assigned wrong field in KOMKBV2.
I have a doubt if KNRZE might work? Plz clarify.
Thanks and i Appreciate your valuable time.

Hi Sumanth,
If you already have plant and storage location in key combination to set the condition record, you just need to maintain the printer name into "Communication" data of condition record in tcode "VV22".
If you don't have plant - St Locn in key combination you'll need
1) Maintain the condition table for fields plant, storage location and delivery type. (path SPRO>LE>shipping>Basic functions>Untruth control>O/P determination>O/p determination for o/b delivery)
2) Assign newly created table to the access sequence which is assigned to condition type. (path SPRO>LE>shipping>Basic functions>Untruth control>O/P determination>O/p determination for o/b delivery-->Maintain Access Sequence)
With above setting you'll be able to maintain condition record with the new key combination and then can maintain the printer 1 for plant "A", st locn "B" and delivery type "LF". Also can maintain printer B for combination "A", "C" and "LF".
Hope this will help.
Regards,
Sudhir

How to re-run output determination after goods issue through idoc

Hello,
i've got a question about output determination. We are currently in a process to automate picking, packing and goods issue through a 3rd party software. The software creates DELVRY03-Idocs including picking, packing and goods issue-information. Picking, packing and goods issue work just find and after submitting the idoc, the delivery is updated as needed.
The problem arises when it comes to printing the shipping document on the printer belonging to the picking station that just processed the delivery. To determine the correct printer, the external software includes the picking station number inside the idoc. A user exit in idoc_input_delivery puts the number (3 digits) into likp-traid. The customizing for using this field inside output determination is complete and seems to be working.
The problem is: as the number of the picking station is not known before goods issue, the LD00 message must not be generated before goods issue. I used the appropriate condition insinde the message scheme, the message is not generated until goods issue is complete. After processing the DELVRY03-Idoc, the message should be found and generated, but it isn't. When i take a look at the delivery after submitting the idoc, goods issue is complete, picking and packing is done - and no sign of an header message of type LD00. First i thought about a misconfiguration inside my customizing for output determination, but when i access the delivery via vl02n (change delivery), output determination seems to be processed again and without making any changes or actions, LD00 is generated and waiting for processing. After saving the delivery, LD00 is processed and the shipping document is printed exactly where it should be.
So, as my customizing seems to work and everything else around idoc processing doesn't make any problems either, i conclude that, after processing the idoc, R/3 just needs a little kick to re-run the output determination, find the now fitting condition for LD00, find the appropriate entry in the condition table and print the document.
I already tried report rsnast00, but this one just seems to run already created messages.
Any ideas how to automate this little "kick in the butt"?
Thanks in advance!

I'm working on a similar issue with ws_delivery_update. I'm not using the IDOC as you are, but I'm using the function in a program of mine to PGI the delivery, but the output isn't being added to the delivery. I've tried to run the function twice as you suggested, but that doesn't seem to work. Do you have any suggestions or ideas on things to try?
Thanks,
Eric

Email PDF file name issue via output determination - order confirmation etc

Hi,
I can email pdf files via output determination. Unfortunately the file name is same as sapscript name. How do I change it to the name I want for example document number.
Thanks,
Jai

Hi Jaideep,
You can change the mail title at Output determination.
T/code NACE--> Application > Outputtype> Select O/P --> select Mail title and texts --> specify your text( with language) in "title" .
Whenever Script send via e-mail the text you have entered will apear as mail title.
Hope this may help you.
Lanka

Output determination ----Urgent

Hi , I got a problem regarding Output determination in SD.
There is credit memo , created based on an invoice. When iam taking the "Print preview " at the header level of the credit memo, " the Reference no./Date "
is not showing anything.
When Iam checking the "Edit" button at the header level and then clicking on the "Processing Log", it is showing the following information:
    1. Object 0062000080
     2. Output type: Order Confirmation
     3. Processing log for program RVADOR01 routine ENTRY
     4. Appl. V1 - Problem during data retrieval -
         Table/structure   VBAK
     5. Window TITLE is not defined for form RVORDER01
     6. Element HEADER_DATA window MAIN is not defined
        for form RVORDER01
     7. Element HEADER_TEXT window MAIN is not defined for
         form RVORDER01
So, plz help me resolve this issue . What is the error and how to resolve this error?? Its an urgent case
Thanks with regards
Sourav Bhaumik

Dear Sourav,
          Chect the output type program RVADOR01 with the help of the ABAPer then debug the program then you can come to know what is the exact problem.
-->Before you Check the output determination assignment to the Creditmemo and output type assignment.
I hope it will help you
Regards,
Murali.
Edited by: Murali Mohan.T on Mar 31, 2008 8:34 AM

Print HU label from Outbound delivery using output determination

Hi,
We have a business requirement to print HU labels from outbound delivery. The steps followed are
1) User executes VL02N
2) User clicks on packing
3) Material is entered to pack. HU is automatically generated.
4) After saving the delivery, output message is triggered.
Output determination is as follows
1) An Z output type is created.
2) Form entry and smartform name is assigned to this output type
Issue:
The issue is when the output message is triggered and the code in the form entry is executed, the handling unit (from nast) is not yet committed in the database. Since it is not updated in the database table, we cannot get any handling unit data to be printed.
Any inputs on how to print HU labels using output determination from outbound delivery is appreciated.
Thanks,
Sandeep

Hi Surya,
Thanks for the reply. But, my question was how to print labels from VL02N when i pack a material on this delivery.
Regards,
Sandeep

Line Item fields for output determination?

Hi Gurus,
we are having this dilemma. we want to create an output type for Purchas Orders which will be automatically triggered thru condition records. however, the criteria should include PLANT and MATERIAL GROUP which we all know as part of Line Item Details.
our problem now is that when the output types are created, our output is not created because the PLANT and MATERIAL GROUP criteria is not satisfied. it is empty.
is there a way to fix this? i'm thinking maybe some abap code or badi to force the value to the kompbea structure can do the trick (as the criteria came from this) but we have tried this and the kompbea field does not get populated.
any ideas? abap fix and configuration is most welcome. <removed by moderator>
thanks.
Edited by: Thomas Zloch on Nov 22, 2010 5:12 PM - please do not offer ..., read rules of engagement

Dear Guru's,
we just facing the already discussed issue that a PO within PLANT from PO-item-level should be part of the PO-output determination. Which userexits have to manipulated to get field PLANT into structure KOMKBEA_FILL especially when PO is still not saved (NO EKKO/EKPO information available) but message is already determined with status "NOT PROCESSED"???
Thanks for an answer.
Regards,
Bernd

Output determination routines

Hi,
I have an enhancement to develop output determination routines for the Output types in the Shipment document to trigger outbound interface to the Freight Forwarder based on the Shipment statuses.
Need to develop 2 routines say 950,951.
SD Shipment :
Output Type      Application      Routine Number
ZE01                           V7                              9XX
ZE02                            V7                              9XX
Routine for ZE01.
For the Shipment document number in the table VTTK (VTTK-TKNUM),check status VTTK-STTRG = 1 (Planning completed) then the Output will be triggered.
Routine for ZE02.
For the Shipment document in the table VTTK table check the status in VTTK-STRRG = 4 (Loading End) then issue the output.
I have created the routines and wrote the code for ZE01 like below.
FORM KOBED_984.
*if status of vttk-sttrg(Overall transportation status) is 1,(Planning completed) then outputtype is triggered.
IF VTTK-STTRG = 1.
SY-SUBRC = 0.
ELSE.
   SY-SUBRC = 4.
ENDIF.
ENDFORM.
This will work fine.?Or I need to consider the shipment document number anywhere.?NAST-OBJECTKEY will hold the document number.?i need to loop it.?or just the sy-subrc check is only required..?
Kindly help..
/Ranjith

Hi,
If you really want to be 100% sure that your requirements are rechecked before output, you need to use your own entry module when processing NASt output
See e.G. in TNAPR for your output type which print program/ form entry is used and replace it by your own entry module : Then you can check your own rules again and cancel before doing the actual output( i.e. don't call the 'processing' form )
( contra : you need make a copy of standard print program )
Alternatively, you could check e.g. the userexits that are triggered when reading the document data to be printed and set the correct return code ( r.g. retcode = 4 when your validations are not met ). This will stop processing also. ( e.g. GET_DATA_USEREXIT )
The correct names of the variables etc..depend on the print program that you are actually using .
( pro : Could maybe be done without copying standard print program )
Is it still standard print program ?
rgds
Dirk

Output determination does not happen during Sales Document creation

Hello All,
I am facing an issue where the automatic output determination does not happen when the Sales Order is created. Let me explain a bit on the background.
Output type ZDL2 has been defined as a special function (TNAPR-NACHA = 8) attached to a custom program and Form routine to create Outbound delivery after successful posting of the sales order.
Condition records are maintained to trigger this output for the Key Combination of Sales Org/Distrib Channel/Division/Route. Access sequence has also been correctly maintained for the above fields.
When the Sales order is saved, the output is supposed to be triggered but out of several sales orders created, it triggered for just one document. We have no clues on what could be the issue.
One question here is, can we have the access sequence maintained for the fields from both header and item level (ie KOMKBV1 and KOMPBV1). Please be reminded that, in our case, the field ROUTE comes from the field catalog KOMPBV1.
Another point which we noticed is that, the Function Module COMMUNICATION_AREA_KOMPBV1 which is supposed to fill the Item data Communication structure for output determination was never called.
Has anyone came across such situations. Comments or suggestions are really appreciated.
Kind Regards
Sabu Kuriakose

Sabu Kuriakose,
Since you are using ROUTE as one parameter for the condition table, and it is at the item level.
the output is triggered at the header level.
So a sales order can contain multiple items with different routes. so at header level how will u identify the route ?
the fields might be available for creatign the condition table but the problem is the fields should get the value during order processing.
in the analsysis screen you will know that the field is getting the value of the ROUTE or not ?
also for creating a delivery you need a shipping point. same as above you can hae multiple items with different shipping points. how will u consider that scenario.
If you can explain that, then that will be helpful to answer your problem.

Output determination process

hi
my issue is how an outputdetermination happens from sales to invoice, please help me out in this process

For getting any output either by print, Fax, or any media you have to do output determination. output determination is also carried by Condition techniques. The detail procedure for Output Determination is :
OutPut Determintaion :
Output is a form of media from your business to one of its business partners or it can be within the organization. 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:
Configuration path: ( following are the steps)
1) SPRO-> IMG-> Basic Functions-> Output Control-> Output Determination-> Output Determination using Condition Technique- >Output Determination for Sales Documents (or you can use output determination for billing documents depending on your requirement).
2) Create Condition Table: select the field Sales Doc Type from field catalog & Save
3) Maintain Access Sequence: 4-digits code & description.
4) Assign condition table to access sequence. Select Accesses line item and Go To Fields. Fields will display the fields we have selected in the condition table i.e. sales doc type.
Maintain Output Types:
AF00: Inquiry
AN00: Quotation
BA00: Order Confirmation
LD00: Delivery
RD00: Invoice
Select BA00 & Copy & Rename. Give the same 4-digit code as given to access sequence.
You Can Maintain:
Languages of Output
Partners (to whom you need 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 and create your own 6-digit code with description. Select the procedure, go to Control Data. Here mention the output type i.e. condition type and 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 organisation/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to whom the output should be sent, time, medium, language.
It contains: Sales Orgnisation, 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.
Path For Output Determination For Sales Documents: Logistics -> Sales/distribution -> Master data -> Output -> Sales Document -> Create (t-code VV11)
Path for Output Determination for Delivery Documents : Logistics -> Sales/distribution -> Master data -> Output -> shipping -> Create ( t-ode VV21)
Path for Output Determination for Billing Documents : Logistics -> Sales/distribution -> Master data -> Output -> Billing Document -> Create ( t- code VV31)

Output determination from customer master

Hi,
I am working in ecc6.0,
i want the output deterrmination procedure should be carried from Customer master.
For this i want to create a new output determination procedure which i can assign to Customer account group.
Can any one please tell me the path to define this output determination procedure.Because it is not available in basic function.
So that i can assign to account group.
thanks

Hi Friend
For Output Detn. following are necessary the steps
1.SD> BF>Output Control>O/P Detn
here define Po det Proc for Sale Doc or Billing Doc ,
a.Selct O/P Type (Maintain Program & Routine)
b.maintain Acc Seqn
c.MaintainO/P Det Procedure & Assign to Sale Doc Type.
If you still have issue witn .
Check out Comm Strategy & Print Paramets too.
Thanks
Saurabh

Output Determination Error

Hi Gurus,
I have already customize the output determination for generating message proposals when creating a sales orden.
It functions correctly, setting the message in "Not Processing " status.
After I run RSNAST00 program, the status of the message change to "Process with errors."
After making some debuggin to the program, I notice that the following fields were empty:
ADRNR
ADRNP
ADDRESS_TYPE
Causing the error message I just explained.
This functionality runs correctly in QAS, but not in PRO.
Do you know why it happens?
Thanks you very much!

Hi Shiva Ram,
I just checked the tx vv22/vv23 and my z output type is not found.
I also checked for the i in va03, and notice the following:
Diagnosis
A valid output condition has been found for the application object.
System Response
An output proposal is created.
Procedure
Execute function
Diagnosis
Output ZVEN has already been issued. Multiple issue for this output type is forbidden in Customizing.
System Response
This output cannot be created again.
Procedure
If you want to issue output type ZVEN several times, set the indicator for multiple transmission in Customizing for this output type in the current application.
The settings in QAS and PRO are the same, do you know why it happens?

Output determination for billing type

hi,
can somebody answer this ,i have a question that,during invoice output determination i need more than one output type to get displayed for selection automatically for a same billing type.
for e,g if i have three output types rd00,xxxx,yyyy.
when i go to vf02 and press issue output then i need all these three output type come automatically,so that i can select from that.
i need the config part pls its urgent.

Hi Ranjeet,
It will be really helpful if you can send me the document to [email protected]
Thanks in advance
Srikkanth

Output Determination Issue

Similar Messages

Maybe you are looking for