Create output determination vv21

Hello!
I need to create an output determination in vv21 for sales organization and delivery type. How i do this?
thx

Fill in the output type (you already have customized).
Click on the key combination button : optionally choose the requested combination (sales org / customer or sales org for instance).
In the table control : fill on the key combination fields and the fields relevant for output creation.
regards,
Hans
Please reward all helpful answers !!!!!

Similar Messages

Sap sd output determination

Can any body help me In customising where we create output determination for DB0001menu path?

Dear Ashok,
DB0001 is not available in Latest release of SAP.
You can use the following transactions in Order to Determine the Output for Sales Documents
For Sales Order
SPRO --> Sales & Distribution --> Basic Functions -->Output Control --> Output Determination Using the Condition Technique --> Maintain Output Determination for Sales Documents --> Assign Output Types To Partner Functions
And For Billing Documents
SPRO --> Sales & Distribution --> Basic Functions -->Output Control --> Output Determination Using the Condition Technique -->
Maintain Output Determination for Billing Documents -->Assign Output Types To Partner Functions
Regards
Vishal
"The Strongest principle of growth lies in Human choice"

Purchase Order and GR document Output Determination and creating own logo o

Can anyone let me know the process of output determination of PO and GR documents.
Also let me know the way to incorporate my own logo on the documents

Hi sudip
For the logo on documents, you have to take help of ABAP ppl.
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
*4. Message Determination Schemas*
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Output of GR
After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document.
Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02

Output determination in Create/Change.

HI Gurus,
          How can I diifrentiate whether Sales order is created or changed in output determination, I'm sending data to XI through a custom IDOC. I want to send different data for creation of order and Change of Order how can I handle this.
          Where should I andle this in a driver program.
          Imeediate soultion awaited.Thanks.
Kind Regards,
Suresh

Hello Suresh,
1. You can track it using sy-tcode and check whether it is VA01 or VA02.
2. Other way is you can check in the Idoc Message type and your Partner profile configuration.Under the Message control, you can find a check box, which would tell you whether you should trigger your idoc on create or change. If it is unchecked, it would send on create and if checked, it will send during change mode.
Thanks!
Suresh Ganti

Sales Order Output - determined by Sales Order Type, Created By

I want have my order output determined by sales order type
(vbak-auart) and created by (vbak-ernam).
I have created a condition table 501, access seqeunce Z001.
In v/48, in accesses for Z001, I created
AcNo: 10
Tab: 501
Requirement: [empty]
Exclusive: unchecked
in fields, I can't find ERNAM in structure KOMKBV1(header), but I find one in KOMPBV1 (item).So I have assigned it to ERNAM.
besides, I have created the corresponding records in VV11
I expect to have:
Output Z001 will be created for sales order type OR if created by user XXX
However, no output is generated. When I go out detemination analysis, I found that in the output determination procedure, it did go into output type Z001, but, since no value is found for "created by", i got message "Access not made (initialized field").
I suspect that no value stored in KOMPBV1-ERNAM. Do you know how I can get it done?
Points will be awarded for useful information. Thanks in advance.

Hi
You have to include this field as a Zfield in the structures KOMKBV1, KOMPBV1 and KOMB.
You have to include the field as Zfield in these structures.
Once this is done, you should also be able to update this field in the structures.(As on now, you have only created a field, but you have not mentioned how the field has to be updated.
In order to update the logic, you have to do a small code in one of the user exits for outputs.
In the user exit, you have to write a code like this
MOVE VBAK-ERNAM = KOMKBV1-ZERNAM(this is the zfield you have created)
Now create the condition table and do the rest.
Your output should work fine. The user exit I was saying is the subroutine USEREXIT_KOMKBV3_FILL in the include RV61B902 in the user exit RVCOMFZZ. If you can give this info to the technical guy, he should be able to find out the same for saels order output also.
The user exit RVCOMFZZ also has the subroutine USEREXIT_KOMKBV1_FILL which you can verywell use for your requirement. This will solve your problem
Hope this helps.
If you have any problems in this, you can again put the problems in this thread. I will try to solve.
Reward if this helps you

Output determination using bapi create order

Hello,
I am using BAPI to create sales order. We have our 'Z' output determination which is connected to the new SD order.
It is also in NAST and has green light . But RSNAST00 did not worked.
This output determination writes a record to a table - but using the BAPI it did not happened.
Any one met this problem?
Thanks in advance
Sara

The green light only means that the output record was processed and that the processing program set the return code value to 0. It does not mean that any particular part of the code was successful. You should check for the success of the DB operation in your code. You can switch the light to Red by using a '4' for the return code. You should also add any necessary (custom) messages to the processing log using NAST_PROTOCOL_UPDATE.

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)

Configuration output type for VL02N - creating output type

Dear Sapguru,
I want to configure output type for VL02N transaction for IDOC creation,Here scenario is to connect SAP to third party system in IS retail.
VL02N- Output type configuration In only return delivery case.
Can anybody guide step by step cycle configuration for output type.Looking forward for your quick reply.
Note: Output type required for IDOC,to communicate with third party system,not for print function.
Thanks.

Dear Anup,
If my understanding is correct,
This seems to be a outbound Idoc scenario where Idoc will be sent by SAP to third party for a return delivery notification.
Output type configuration steps are as follows :
1) Identify the standard output type (Application - V2, Transmission Medium - 6 ) for e.g. LAVA which is very close to your requirement.
2) Use this output type as a reference & create a copy output type of your own.
3) Use a suitable access sequence or create your own access sequence as per your requirement.
4) Assign access sequence to the output type.
5) Maintain output determination procedure (connect your output type to a suitable procedure )
6) Assign output determination procedure. (to your delivery document type)
7) Maintain required output condition records through T Code - VV21 against your newly created output type.
8) Set up the partner profiles as per your requirement (T code - WE20)
9) Check the reflection/ effects of your new output setup at the delivery document level (VL02N).
You may quickly access these settings through T codes - NACE.
Tables - TNAPR, NAST
Hope it will help you in the set up.
BR,
Anubhav

Output Determination in Delivery and billing

Hi Gurus,
Can anybody tell me how to maintain output determination for delivery. i have maintained Condition record for LDOO but when in delivery i goto Extras-output-header it taked me back to the same setting of LDOO. How do i see the output for delivery.

Hi,
Complete the condition technique for output determination for outbound dellivery.
IMG-logistics execution-shipping-basic shipping functions-output control-output determination-maintain output determination for outbound deliveries.
Create the condition table, access sequence, condition type, procedure and assig the output type LD00 to the procedure. Assign this procedure to your delivery document type.
Maintain the condition record for outbound deliveries in VV21. Select LD00, enter Sales Org, customer no. of Ship to party, SH partner function. Select the line item an click on communication, select the printer and save the settings.
Now you have created the delivery in VL01N. Save the delivery. Now go to VL02N, select the delivery number, In the menu bar in outbound delivery, click on issue delivery output. Her select the output type and click on print preview.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

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

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

No output determined for GR slip

Hi Experts,
Need your help to analyze a situation.
My system is not able to determine a output condition record for a material document for GR. The system ends up in a error "The system could not create any outputs". Although the system immediately generates a output when the printer name is filled in the condition records.
Settings currently done in the system:-
- Proper customizing exist in the system for output detrmination for Inventory management.
- Print parameters for WE01(individual slip) is set to S "User parameters".
- Condition record maintained for WE01 with dispatch time 4 for a "print" output. The printer field is kept blank.
- User parameter NDR not Set. The check box XNAPR is checked manually.
- A printer is set in the User parameters -
>Defaults -
Output device -
ML0001(physical printer).
OSS notes already checked:-
446041 (sympton 2 applies, but it doesnot help).
426554 (all settings done as per the checklist)
The system should act as below but unfortunately it doesn't.
The system checks whether a printer has been specified in the condition record. If so, it is used. If not, it checks the message type to see whether a print parameter has been set. If no parameter has been set, no message is generated. If a parameter has been set, a printer is sought in accordance with this parameter. If a printer is found, it is used to output the message. If not, no message is generated.
Please help me with your expertise.
Regards
Raj
Edited by: RajKiran Mohanty on Mar 8, 2012 4:31 AM

Hi,
I am not sure but check this
sap 426554: check lists for output determination and printer determination for goods movements
Checklist 2: Check printer determination Customizing
1. Which printer do you want to use?
Printer: _____
Is the printer defined in the MM-IM Customizing? (Customizing MM-IM > Print Control > General Settings > Printer setting)
Entry exists: _ yes / _ no
2. Does the condition record have a fixed printer (see question 6 of checklist 1)? (Customizing MM-IM > Output Determination > Maintain Conditions > Communication). Note that it does not usually make sense to define a printer in the condition record otherwise all messages are printed with this printer.
Printer in condition record: _ yes: Printer ______ / _ no
3. Which print parameter does the output type have? (Customizing MM-IM > Output Determination > Output Types)
_ Plant/storage location (7)
_ Plant/storage location/user group (9)
_ User (combination of output type/user name) (U)
_ User parameters (printer from user master record) (S)
a) Printer determination according to plant/storage location (7)
Which plant/storage location do you use?
Plant: ____ Storage location: ____
If the purchase order has an account assignment, the storage location is initial.
Is there an entry for the printer determination with the above combination? (Customizing MM-IM > Output Determination > Printer Determination)
Entry exists: _ yes / _ no
b) Printer determination according to plant/storage location/user group (9)
Which plant/storage location do you use?
Plant: ____ Storage location: ____
If the purchase order has an account assignment, the storage location is initial.
With which user is the material document posted? (See question 7 of checklist 1)
User:________________
Which value does parameter ND9 have for this user (display user master record > parameters)
Parameter ND9 (user group): __________________
Is there an entry for the printer determination with the above combination? (Customizing MM-IM > Output Determination > Printer Determination)
Entry exists: _ yes / _ no
c) Printer determination according to user (output type/user name) (U)
With which user is the material document posted? (See question 7 of checklist 1)
User:________________
Is there an entry for the printer determination with the above combination? (Customizing MM-IM > Output Determination > Printer Determination)
Entry exists: _ yes / _ no
Have you mark fixed indicator for printer?
Regards
Kailas Ugale
Edited by: kailasugale on Mar 8, 2012 2:14 PM
Edited by: kailasugale on Mar 8, 2012 2:16 PM

Output determination for PO

Hi, I don't have much knowledge,waht are the steps and settings required to maintain output determination for purchase order and material document.
Thank you.

Hi,
PO Output
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
GR Output
Output of GR
After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
Regards,
Biju K

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

Create output determination vv21

Similar Messages

Maybe you are looking for