Output management [ REV]
Functions
- Retrigger Sales order output after changes at partner only
- Send message for Purchase order
- Invoice verification: Creating message records ( 22.09.21 )
- 960611 - FAQ: Output control in SD
- 2313029 - Output Management in S/4 HANA for Physical Inventory Default Customization
- 2274936 - Output Management in S/4 HANA for Goods Movement Default Customization
- 2330928 - Output Management in S/4 HANA for Sales Document Default Customization for On-Premise Systems
- 2344602 - Is it possible to use the NAST output logic in S/4 HANA instead of default S/4HANA Output Control in purchasing documents?
- 2267444 - S4TWL - Output Management Adoption in Purchase Order
- 457497 - FAQ: Message processing in purchasing
- 522591 - FAQ: Output determination in inventory management (IM)
SAP Reference IMG -> Cross-Application Components -> Output Control -> Manage Application Object Type Activation
For the SAP S/4HANA output control, configuration is different than for NAST-based output management and must to be created in the Output Parameter Determination (BRF+). For technical and implementation details, please refer to simplification item “Output Management” (SAP Note 2228611).
Functions
Send message for Purchase order
Go to transaction XK02, enter the vendor number and select General data –> Address. Maintained the E-Mail address in the Communication section.Note that you can enter more than one email address, but the system will only sent the email to one of them. You can select which will be use as default thru button: “St..” (Standard Sender Address in this Communication Type).
We can also set email address at Persons for this business partner.
For 4.6C you need to:
1. Define partner functions for your vendor. To do this assign paretner=
roles to yout account group in transaction OMZ3. Then update your vendor=
with the partner roles in XK02. We email our PO’s to the vendor himself=
which means partner function VN needs to be defined.
2. Define a partner schema (0002) for your purchasing document type in=
transaction OMZ7. =20
3. Define new output types if needed and define partner functions for=
output types in transaction M/34. You can use NEU to email etc, but if you=
want to print and email the same PO you need to define another output=
type.
4. If you have defined a new output type you need to define the message=
determination schema for it.
5. If you have defined new output type you need to define partner roles per=
output type.
6. Create conditon records in transaction MN04 for your output type and=
purchasing doc type. You need to define the partner role that will receive=
the email. YourMessage transmission medium will be 5 (External send. Time=
will be 4 (send immediately when saving). Communication strategy will be=
CS01. Even though you do not print you need to specify an output device.=
Tick print immediately if you want the PO to ptint if the system find no=
email address on the vendor.
7. Make surethe vendor’s email address is maintained on the vendor master.
8. Make sure that the userid creating the PO (emailing the PO) has an email=
address maintained in its user profile (SAP uses this email address as the=
from email address).
1. Define partner functions for your vendor. To do this assign paretner=
roles to yout account group in transaction OMZ3. Then update your vendor=
with the partner roles in XK02. We email our PO’s to the vendor himself=
which means partner function VN needs to be defined.
2. Define a partner schema (0002) for your purchasing document type in=
transaction OMZ7. =20
3. Define new output types if needed and define partner functions for=
output types in transaction M/34. You can use NEU to email etc, but if you=
want to print and email the same PO you need to define another output=
type.
4. If you have defined a new output type you need to define the message=
determination schema for it.
5. If you have defined new output type you need to define partner roles per=
output type.
6. Create conditon records in transaction MN04 for your output type and=
purchasing doc type. You need to define the partner role that will receive=
the email. YourMessage transmission medium will be 5 (External send. Time=
will be 4 (send immediately when saving). Communication strategy will be=
CS01. Even though you do not print you need to specify an output device.=
Tick print immediately if you want the PO to ptint if the system find no=
email address on the vendor.
7. Make surethe vendor’s email address is maintained on the vendor master.
8. Make sure that the userid creating the PO (emailing the PO) has an email=
address maintained in its user profile (SAP uses this email address as the=
from email address).
Retrigger Sales order output after changes at partner only
After you change certain attribute values (data) in objects (documents), the system must automatically create a change output. Since there are many options for defining change outputs, you must always perform a customer-specific adjustment. In the standard SAP system, no routines are available that support the processing of change outputs.
For the output type on which the change output is based, you must make the following settings in Customizing (detail view of an output type):
- In the general data, you must set the "Multiple issuing" indicator.
- In the section for change outputs, a form routine (field label: 'T685B-AROUT') from the program (field label: 'T685B-APROG') must be assigned to the output type. You are not allowed to use the form routine of a print program.
The process is as follows:
- If the same output is found during a new document processing, the assigned routine is executed by an external program call (this external program call is performed in the subroutine NNAST_AENDE_CHECK of the include LV61BF0N).
- The routine must set a return code using the system field SY-SUBRC. If the value is equal to zero, the system creates an output; if the value is other than zero, it does not create an output.
- If the system creates an output, the system sets the "Change message" indicator in the output record (field NAST-AENDE).
Since the output determination is started during document processing, we recommend that you run the routine in the relevant programs. Then the required data of the document (old and new status) is available. This would mean, for example, to use the following programs and to assign the required form routines to the following includes of the relevant user exits:
- Sales order SAPMV45A ZZ_ORDER_CH (include MV45AFZZ)
- Delivery SAPMV50A ZZ_DELIV_CH (include MV50AFZZ)
- Billing document SAPLV60A ZZ_INVOIC_CH (include LV60AFZZ)
The Y variables contain the old data, the X variables contain the new data (exception current order header). The objects are always represented by a header structure (K) and an item table (P). In the case of a sales order, the additional schedule line table (E) exists.
he procedure can be illustrated by a simple example.
If an item is added to an order or deleted from an order, the confirmation (here, output type BA00) must be printed again. All other changes are ignored.
First, a form routine ZZ_ITEM_CHECK is created in the user exit MV45AFZZ. The source code may then look as specified below.
If the change indicator is set to "Insert (I)" or "Delete (D)", the change is relevant and the return value is set to zero. As a result, the system creates a change output. By processing the output, the relevant print program is executed. This print program prints out the complete order confirmation.
Finally, a few important remarks about possible problems are mentioned:
1. First, within identical outputs, there can be only one output that is not processed. If several relevant changes to an object are performed one after the other and the relevant output is not immediately processed, the old output receives a new time stamp. In the above example, this is not relevant because the system always prints the complete confirmation. A problem occurs if the last change restores the initial status before the last printout: The system prints the same confirmation. You can only avoid this if the change history of an object is available. This is only the case in the order (see change documents). It is also useful to print out only the actual changes, that is, the items that have been changed.
2. A further problem may occur if there is a relevant change and subsequently, an output is created but not processed. Then an irrelevant change is performed in the document. In this case, the output that has not been processed yet, must be retained.
Invoice verification: Creating message records
Logistics Invoice Verification -> Message Determination -> Maintain Message Types- KONS Consignment
- KON6 Consignment EDI
- REKL Complaint
- ERS ERS Procedure
- ERS6 ERS Procedure EDI
- MLPP Mail Price Deviation
- RAP New Value Method
- RAP6 New valuation EDI
- INS Invoice plan
Invoice Verification -> Message Determination -> Maintain Message Schemas
Invoice Verification -> Message Determination -> Maintain Conditions "Create Output" or "Change Output" (if it exists)
Additional information
960611 - FAQ: Output control in SD
1. Question: Why does the system not print the sales text defined in Customizing when the terms of payment are printed out?
Answer: This field is not printed in the standard system. For more information about this, see SAP Note 532654.
For more information about printing terms of payment in Sales and Distribution, see Note 101518.
2. Question: Is there a transaction for the collective printing of outputs from orders (such as VF31 for "Output from Billing" or VL71 for "Output from Deliveries")?
Answer: As of Release SAP ERP Enhancement Package 5, transaction VA71 is available. Also see SAP Note 2784287.
In the older releases, there is the following alternative:
The relevant transactions for outputs from sales process documents are always based on an SD70A* report: VL71 -> SD70AV2A, VF31 -> SD70AV3A, and so on.
Such a report also exists for outputs from orders: SD70AV1A. You can either directly execute this report or assign it to a customer-specific transaction.
3. Question: Why does the system not issue outputs in the expected sequence when sales documents are collectively printed?
Answer: This is the standard system behavior.
- The sequence of the outputs in the output determination procedure does not have any influence on the sequence of the outputs during printing.
- The system ignores the sequence in which the outputs were inserted into a document.
- The system does not automatically sort according to customers when it issues outputs.
In Sales and Distribution, the outputs in a document are repeatedly sorted in internal tables during output determination and output processing.
Please use the sort criteria of the relevant transaction (for example, VF31) or the sort criteria of the relevant report (for example, RSNAST00) for issuing outputs.
4. Question: Can you use further sort criteria in addition to those proposed in the "Sort order" field for printouts from sales and distribution documents (for example, transaction VF31 or VL71)?
Answer: Yes, the following options are available for this:
a) In customizing for the output type, you can specify up to three additional sort fields from the relevant print structure (print structure KOMKBV1 for application V1, KOMKBV2 for application V2 and so on).
You can then use these fields as "Sort fields 1-3" using sort criterion 04 and 05.
b) If this is not sufficient, you can use the user exit RSNASTZZ for the customer-specific sorting of the outputs during processing with the report RSNAST00.
For more information, see Note 357114.
2267444 - S4TWL - Output Management Adoption in Purchase Order
2274936 - Output Management in S/4 HANA for Goods Movement Default Customization
2313029 - Output Management in S/4 HANA for Physical Inventory Default Customization
For Physical Inventory, the set of business rules is represented by an Application Object and an Output Type. The Application Object is defaulted to PHYSICAL_INVENTORY. An Output Type is defined for each type of Physical Inventory requiring output. When the business rules are applied by Output Management, attributes obtained from the Physical Inventory Document and the selection of transaction MI21N are used to determine the type of output to issue, the receiver of output, the channel used to issue the output, the printer settings (only applicable for Output Channel PRINT), e-mail address of sender/receiver (only applicable for Output Channel EMAIL) and the form template used to generate a PDF document. Refer to Default Customizations - SAP GUI On-Premise and FIORI Cloud in the Solution section of this note.
The Form Template used by Output Management to generate a PDF document contains a data source (OData Service) and the layout of a PDF document (Adobe Livecycle Design Document). The OData Service retrieves the data for the Physical Inventory Document from the database and the result is merged with the Adobe Livecycle Design Document to render a PDF document representing the count list of a Physical Inventory Document.
Output Management will track the status of each output to be issued. The following statuses can be generated by Output Management during the process of creating the output and issuing the output.
After creating the output with transaction MI21N, you can view the created outputs via the function "Manage requests" to display or change the generated output requests. To open the Output Management window, just double click on an exsiting output request.
Scheduled issuing of output for Physical Inventory Documents can be activated optionally using the dispatch time 2 in the Business Rules. To process the scheduled outputs, the program RM07IDRUN with select option "Process scheduled" has to be used.
Limitations: Output for Goods Movements is only issued by Output Management for the output medium type PRINT. The output medium types XML , EMAIL and IDOC are not currently supported
457497 - FAQ: Message processing in purchasing
1. Question:
I use my own print program and form for printing. Where can I find basic information about troubleshooting?
Answer:
Before you create a customer message, assign the standard entries (for example SAPFM06P for the print program and MEDRUCK for the form when using purchase orders) and check to see whether the problem also occurs in the standard system.
SAP support cannot help you with problems that occur only when you use your own print programs/print forms or occur only in connection with modifications to standard print programs and standard forms. If you require help to correct an error, contact consulting.
See SAP Note 111062.
-----------------------------------------------------------------------
2. Question:
I send a purchase order with transmission medium 'FAX' and I want to receive a confirmation of the sent fax in my office inbox.
Answer:
See SAP Note 457337.
-----------------------------------------------------------------------
3. Question:
The sorting in the message detail of the print program does not correspond to the sorting during output. This symptom occurs in Release 4.0B only.
Answer:
See SAP Note 456371.
-----------------------------------------------------------------------
4. Question:
I am using a message output transaction (ME9A, ME9E, ME9F, ME9K, ME9L) and I want to view documents that have already been output.
Answer:
see KBA 2573469
-----------------------------------------------------------------------
5. Question:
What role does the user master data play during message determination?
Answer:
See SAP Note 446041.
-----------------------------------------------------------------------
6. Question:
For an outline agreement, I want to output messages to the partner ordering address, but the system finds an incorrect message record or it does not find any records at all.
Answer:
see KBA 2576614
----------------------------------------------------------------------
7. Question:
In the communication data of a message condition, I have maintained the 'Authorization' field so that I can regulate the display of the spool request (transaction MN05 or MN04). However, this authorization entry is not transferred to the message records of the purchasing document and an authorization check does not occur.
Answer:
See SAP Note 444916.
-----------------------------------------------------------------------
8. Question:
When using transaction ME90 for the message output I notice a potential program error.
Answer:
See SAP Note 444876.
-----------------------------------------------------------------------
9. Question:
On the initial screen of the print program (transaction ME9F), you change from the application "EF" to a different purchasing application (EA, EL, or EV). Afterwards, no documents are displayed.
Answer:
see KBA 2584126
-----------------------------------------------------------------------
10. Question:
I enter an inbound delivery for a purchase order. Afterwards, the system updates the inbound delivery in the purchase order, however, it still proposes the inbound order for expediting in the order acknowledgment expediter (ME92F).
Answer:
see KBA 2584079
-----------------------------------------------------------------------
11. Question:
During the output of purchasing documents, the system displays error message ME 142 "Error in OPEN_FORM for document &" in the message log. How do I analyze this error?
Answer:
See SAP Notes 397691 and 532251.
-----------------------------------------------------------------------
12. Question:
Why does the system generate change messages when the change is non-print-relevant?
Answer:
See SAP Note 28869.
-----------------------------------------------------------------------
13. Question:
I attempt to re-issue a processed change message using the 'Repeat message' button. The system displays message ME 780 or ME 140 saying that no changes have been found.
Answer:
See SAP Note 391637.
-----------------------------------------------------------------------
14. Question:
When I change a purchase order item, no long text is displayed in the change message.
Answer:
See SAP Note 373524.
-----------------------------------------------------------------------
15. Question:
I maintain texts in a purchase order. The formatting I used is ignored during printing.
Answer:
See SAP Note 372606.
-----------------------------------------------------------------------
16. Question:
Why are some texts not printed at all?
Answer:
Which texts are printed depends on the Customizing settings of purchasing.
Go to Customizing for purchasing.
Choose "Messages -> Texts for Messages -> Define Texts for <Purchasing Document>". Choose "Print Document <Purchasing Document>". Select "Texts for Document Items" and add a new entry.
You must specify a value for the print sequence in the detailed screen for your new entry.
-----------------------------------------------------------------------
17. Question:
I have created a purchase order and I have already posted a goods receipt (GR) quantity for it. I want to display the quantity that is to be delivered for the purchase order data.
Answer:
See SAP Note 371490.
-----------------------------------------------------------------------
18. Question:
I branch to the print preview for a purchase order in EnjoySAP transaction ME21N, ME22N, or ME23N. It may happen that too much or not enough data is displayed. However, the document is printed correctly.
Answer:
see KBA 2584088
-----------------------------------------------------------------------
19. Question:
The print program no longer works in purchasing.
Answer:
See SAP Note 324453.
-----------------------------------------------------------------------
20. Question:
The system displays the delivery address incorrectly or incompletely.
Answer:
See SAP Notes 214907 and 492055.
-----------------------------------------------------------------------
21 Question:
Which communication types can I use in a communication strategy?
Answer:
see KBA 2584174
-----------------------------------------------------------------------
22. Question:
I have created a purchase order that is not yet released. In transaction ME90, this purchase order is displayed in the list but not yet printed.
Answer:
See SAP Note 313850.
-----------------------------------------------------------------------
23. Question:
The unloading point I maintained in the account assignment and the goods recipient are not included in the purchase order printout.
Answer:
See SAP Note 311571.
-----------------------------------------------------------------------
24 Question:
A purchasing document message was processed (successfully or incorrectly), but no processing log was generated.
Answer:
see KBA 2584228
-----------------------------------------------------------------------
25. Question:
In certain situations, I want the title of the message (NAST-TDCOVTITLE) to be variable and to contain information such as the document number.
If an error occurs during fax output, I want a mail to be sent to the creator of the purchasing document or message.
Answer:
See SAP Note 120474.
-----------------------------------------------------------------------
26. Question:
How can I send a purchase order as an e-mail and which setting options are there? Where can I find help about troubleshooting?
Answer:
See SAP Note 191470.
------------------------------------------------------------------------
27. Question:
How can I archive faxed messages?
Answer:
See SAP Note 134845.
------------------------------------------------------------------------
28. Question:
Why are no messages generated when the system creates purchase orders automatically?
Answer:
See SAP Note 321209.
------------------------------------------------------------------------
29. Question:
Why do problems occur with stock transport orders?
Answer:
See SAP Note 407600.
------------------------------------------------------------------------
30. Question:
Can documents that are linked (attached) to a purchase order also be included with the message output?
Answer:
see KBA 2584312
------------------------------------------------------------------------
31 Question:
How do I maintain fields relevant for the printout of changes and change texts?
Answer:
See SAP Note 512700.
------------------------------------------------------------------------
32 Question:
The target quantity was changed in a request for a quotation. How do I suppress the output of the change message?
Answer:
In Customizing for the print-relevant fields, the checkbox that indicates the print-relevant data for requests for quotations must be deactivated for the fields 'EKPO-KTMNG' and 'EKET-MENGE'.
You can find more information about Customizing for print-relevant fields in Note 512700.
------------------------------------------------------------------------
33. Question:
How does the message processing occur with documents that are subject to a release strategy (locked documents)?
Answer:
See SAP Note 61871.
------------------------------------------------------------------------
34. Question:
Is message determination possible at item level too?
Answer:
No. During message determination, the system does not access the data of the purchasing document's individual items (for example, table EKPO or EKET) because the values in the item-related table fields (for example, EKPO-WERKS) may be different from item to item.
------------------------------------------------------------------------
35. Question:
The field for the telephone number that you can specify for a purchasing group is too short. There is no field for specifying the e-mail address.
Answer:
With R/3 Release 4.70, a Support Package provides new fields in the table of the purchasing groups (T024) for storing longer telephone numbers and an e-mail address.
For more information, see Note 559396.
------------------------------------------------------------------------
36. Question:
In an EBP scenario, how can I send information about failed message transfer to the creator of the purchasing document in EBP?
Answer:
See SAP Note 561593.
------------------------------------------------------------------------
37. Question:
Why is the language of the purchasing document always used during message output instead of the language of the message record?
Answer:
See SAP Note 89899.
------------------------------------------------------------------------
38. Question:
Why are the specified decimal places for a unit of measurement not used in the print output?
Answer:
See SAP Note 569326.
------------------------------------------------------------------------
39. Question:
Can data from the purchase order item be used for defining access sequences in message determination?
Answer:
In purchasing, message determination can only be carried out using the header fields. See also Note 39462.
------------------------------------------------------------------------
40. Question:
Why does determination analysis not work when purchasing documents are displayed?
Answer:
see KBA 2584322
------------------------------------------------------------------------
41. Question:
Why does the replacement of text variables not work?
Answer:
see KBA 2584341
-----------------------------------------------------------------------
42. Question:
In Customizing, I have configured the partner role OA (ordering address) for message determination and I have assigned this role to the vendor master. Why is message determination nevertheless performed for the corresponding vendor (role VN) and not for the ordering address (role OA)?
Answer:
see KBA 2584303
-----------------------------------------------------------------------
43. Question:
Why does the message output fail with transmission time-spot 4 (for sending immediately), whereas the output with transmission time-spot 3 (for sending with an application-specific transaction) works correctly? For example, the system issues error message ME 571 or a change message does not contain the data of the current change.
522591 - FAQ: Output determination in inventory management (IM)
Questions
1. Where can you find more detailed information on the topic of output determination?
2. When I print goods receipt/issue slips for goods movements, various problems occur, for example:
- No goods receipt/issue slip is generated or printed
- The goods receipt/issue slip is output on the incorrect printer.
How can these problems be solved?
3. When I send a missing part mail during the goods receipt, various problems occur, for example:
- No missing part mail is sent during the goods receipt
- The missing part mail contains no data or the text variables
are not replaced
- The missing part mail cannot be executed
(the parameter for mail processing is not set)
How can these problems be solved?
4. When printing the collective slip, is it possible to issue a collective label that contains all the items of the collective slip?
Why is only one label printed for each collective slip item and no overall label when print version 3 (collective slip, WEVER=3) and version WEE3 are selected?
5. In transaction MIGO, I cannot enter the version for the goods receipt/issue slip (individual slip, individual slip with inspection text, collective slip) manually. The version is taken from Customizing. How can this be changed?
6. In transaction MIGO, I cannot enter the number of GR slips manually during a goods movement. How can this be changed?
7. Labels are no longer printed when a goods movement is posted using transaction MIGO. The number of GR slips is 000. How can this problem be solved?
8. Why are the partner roles of vendors and customers not supported during goods movements in inventory management?
9. When you enter a material document, you set the number of goods receipt/issue slips (MSEG-WEANZ) to zero to avoid printing a goods receipt/issue slip. Why does the system still print a goods receipt/issue slip?
Comments
Post a Comment