Output Management Configuration Guide

2y ago
29 Views
2 Downloads
900.70 KB
76 Pages
Last View : 17d ago
Last Download : 3m ago
Upload by : Tripp Mcmullen
Transcription

SAP Transportation ManagementOutput Management Configuration GuideCUSTOMERDocument Version: 3.2 – December 2013 SAP AG1

Copyright Copyright 2013 SAP AG. All rights reserved.SAP Library document classification: PUBLICNo part of this publication may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed without priornotice.Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors. National product specifications may vary.These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informationalpurposes only, without representation or warranty of any kind, and SAP Group shall not be liable forerrors or omissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying such productsand services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.Please see dex.epx#trademark for additionaltrademark information and notices. SAP AG2

Icons in Body taxAdditional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help General Information Classesand Information Classes for Business Information Warehouse on the first page of any version ofSAP Library.Typographic ConventionsType StyleExample textExample textEXAMPLE TEXTExample textExample text Example text EXAMPLE TEXT SAP AGDescriptionWords or characters quoted from the screen. These include field names, screentitles, pushbuttons labels, menu names, menu paths, and menu options.Cross-references to other documentation.Emphasized words or phrases in body text, graphic titles, and table titles.Technical names of system objects. These include report names, programnames, transaction codes, table names, and key concepts of a programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.Output on the screen. This includes file and directory names and their paths,messages, names of variables and parameters, source text, and names ofinstallation, upgrade and database tools.Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.Variable user entry. Angle brackets indicate that you replace these words andcharacters with appropriate entries to make entries in the system.Keys on the keyboard, for example, F2 or ENTER.3

Table of ContentsOutput Management Configuration Guide . 51 Definitions . 62 Output Management Overview . 83 Features of Output Management . 133.1 Immediate Print . 143.2 Automated Output . 153.3 Originals and Copies . 163.4 Mass Output . 173.5 Features of the Output Management UI. 184 Output Management Settings and Configuration . 234.1 Maintaining PPF Settings . 244.1.1 Defining Applications . 254.1.2 Defining Action Profiles. 264.1.3 Creating Action Definitions . 274.1.4 Defining Processing Types . 284.2 Creating Conditions . 294.3 Output Management Adapter Configuration . 304.3.1 Customizing . 314.3.2 PPF Exits . 364.3.3 Output Management Callbacks . 384.3.3.1 Action Profile Determination . 404.3.3.2 Action Determinations and Schedule Condition Checks . 414.3.3.3 Start Condition Check . 424.3.3.4 Determine Printer . 434.3.3.5 Determine Document Partners . 444.3.3.6 Determine Partner Language . 454.3.3.7 Specify Output Content for PDF Forms . 464.3.3.8 Specify Application Keys for Transient Action Definitions . 474.3.3.9 Specify Application Keys for Aggregate Action Definitions . 484.3.4 BRFplus Applications and Functions . 514.4 BO Modifications for Integration with Output Management Adapter . 524.5 Configuring Direct Output . 534.6 Configuring the Output Management User Interface . 544.7 General Recommendations and Guidelines . 555 Testing Output Management in Your Application . 576 Appendix . 596.1 Basic Introduction to the PPF . 606.1.1 Configuring Different Output Requirements . 616.1.1.1 Processing Type (Medium Type) . 626.1.1.1.1 Setting Up Processing Types for External Communication . 636.1.1.1.2 Setting Up Processing Types for Alerts . 646.1.1.1.3 Setting Up Processing Types for Method Calls . 656.1.1.2 Action Definition (Trigger Type) . 666.1.1.3 PPF Action Profile (Context Type) . 676.1.1.4 PPF Application . 686.1.2 PPF Runtime . 696.1.2.1 Generating Triggers (Actions) . 706.1.2.2 Processing Triggers (Actions) . 716.2 Design . 726.3 TM-Specific Guidelines . 73 SAP AG4

Output Management Configuration Guide SAP AG5

1 DefinitionsThe following terms are used throughout this document:TermDefinitionActionThis is a runtime instance of an action definition.Action definitionAn action definition is metadata or a skeleton of a business task. Itencompasses all possible realizations (also see processing type).It determines whether business partner data is required for theexecution and the business partner to which the data relates.Within the action definition, you set up the merge technique, thatis, how many successful, failed, or unprocessed actions areallowed for a particular action definition.Action determinationThis is the runtime interface of the Post Processing Framework(PPF). When the action determination is triggered, the PPF checksthe scheduling conditions of all configured action definitions basedon the data provided by the context. The partner is also identifiedfor partner-dependent action definitions, that is, partners with thespecified partner function are added whenever they are providedas part of the partner collection. Otherwise, the partner-dependentaction is deleted. Finally, the specified merge technique istriggered. Execution management is automatically updated for newactions.Action profileSmallest set of action definitions that can be investigated duringone call of the action determination of the PPF.Application objectThe application object is the standardized proxy used to accessthe business object. The persistence of this object must berealized using the object services.Business objectObject that contains the main data that is relevant for actiondetermination and execution. Its persistence is either given as aBusiness Object Repository (BOR) object or as a persistent classof the object services.Configured action definitionThe action definition must be configured so that an action can becreated during action determination. The combination of theselected processing type, scheduling condition, and startingcondition is called a configured action definition. An actiondefinition can have several configured instances. Moreover, almostall of the technical settings for the action definition can beconfigured differently.ContextSet of data transferred to the action determination. The contextincludes the name of the application, the action profile, theapplication object, and a collection of partners.Merge techniqueAs part of action determination, new actions are merged with theold actions of an action definition. You specify the mergetechnique to be used at action definition level. For example, themerge technique 1 successful action per action definition deletes SAP AG6

all newly determined actions if an action in the specified actiondefinition is successfully executed.PartnerAction definitions can be assigned to special person groups. Toidentify these groups, the PPF expects the partner function to beincluded in the address data (for example, “Responsible Person”or “Customer”). The partner number can also be entered ifrequired. An object that contains all of these attributes is known asa partner. The partner functions are defined using a BAdI from theapplication.Partner collectionThis is the runtime collection of all partners in a business object.The collection is part of the context.PPFPost Processing Framework. This provides SAP applications witha standardized way of executing and managing conditionedbusiness tasks. In contrast to the SAP Business Workflow, thesebusiness tasks are mutually independent, meaning that there is noscope for a process flow.Processing typeThe processing type refers to the technical realization of an actiondefinition. For example, start a workflow, send a PDF-based formby e-mail, and so on. SAP AG7

2 Output Management OverviewThe basic functions of an output management system are to: Issue business documents in response to certain business events. The following can beissued:oExternal communication such as printouts, faxes, and e-mails with a printpreview optionoAlertsoWorkflowoBusiness-to-business (B2B) and application-to-application (A2A) communicationoBI data uploadoEvents to an Event Management system on the basis of decisions or in responseto business events (for example, when a forwarding order is confirmed in atransportation scenario)Easily configure:oPrint formsoBusiness decisions to schedule and execute outputsoData extraction to print formsOutput of business documents with the following capabilities:oAutomated (back end), rule-based dispatching of outbound communications inresponse to business events such as the creation of an order, the release of atendering request, and so onoPreview of output and manual (front end) outputs in user interface (UI) scenariosoArchive output dispatched in relation to business documentsoInclude actual print files (PDFs, and so on) in the archive system for bookkeepingand later referencesoMass output from a worklist Optimize performance in relation to SAP Transportation Management 8.0 Provide a comprehensive output management UI that: SAP AGoClassifies all the outputs based on the processing status that can be audited ormonitored. The system triggers and executes the outputs in relation to abusiness document.oSupports archiving, previewing, and log displayoEnables users to generate, activate, or deactivate actions prior to execution8

oEnables users to change the printer, number of copies, communication partner,output language, and recipients prior to executionoEnables e-mail text to be added for the e-mail recipientsoEnables attachments (that are either predetermined using a BAdI, configured inCustomizing, or uploaded into the attachments folder of the consuming BO) to besent to the e-mail recipientoEnables users to choose the mode of communication such as print, e-mail, or faxfor outputting the documentoEnables users to use a default text for the subject line of an e-mail and enablesthem to change the subject textoEnables users to view the list of all relevant actions for a given documentoEnables users to use Customizing settings to generate and execute actionswithout applying rules that would otherwise applyExternal Communication –printouts, e-mails, and cation –Leading BOOutputManagementAdapterA2A/B2B Method CallsBI Data UploadTrigger Events to EventManagementOverview of Output Management AdapterOutput management adapter (developed in the SAP BS FND layer) enables output to betriggered for a given BO node developed in the Business Object Processing Framework (BOPF)environment.Output management (SAP BS FND 702 SP05) uses the Post Processing Framework (PPF).You can connect the PPF at the level of the individual BO nodes. You can also set up PPFtriggers on a BO node-specific (use case) basis and specify whether they are critical or noncritical. SAP AG9

Service Consumer –Web Dynpro UIBOPF Framework –Consuming BOsPPF Adapter for Output Management(Suite Foundation)SAP NetWeaverOverview of Output Management IntegrationThe following figure shows the logical connection of the PPF to BOPF BO nodes: SAP AG10

BO ModelPPFPPF Application(/SCMTMS/ TRANSP MGMT)Business Object11**Node1*PPF Action Profile(Context Definition)11**ActionPPF Action Definition(Trigger Type)0.110.11One or more PPF actionprofiles can be assignedto any BO nodeinstancePPF ScheduleCondPPF Start cond*PPF Processing TypeLogical Connection of the PPFThe PPF must be connected to these nodes whenever outbound communication is required. Thefigure above shows where the PPF for output management must be configured. For moreinformation about the PPF actions that are relevant for your application, see the Modeling Guidefor PPF.The following figure shows the integration of PPF Customizing and the PPF runtime to theconsuming application: SAP AG11

CustomizingAction ProfileAction DefinitionsAction Definition 1Action Definition 2Action Definition 3Action Definition nPPF run timeSet of Action Definitions needs to be generatedand tifying the actionsfor which triggers needto be generatedGenerate Triggersfrom configuredAction DefinitionsStartConditionsIdentifying the triggersthat need to beexecutedExecute TriggersIntegration of PPF Customizing and PPF Runtime SAP AG12

3 Features of Output ManagementOutput management contains an adapter that is developed in the BS FND layer. It uses the postprocessing framework (PPF), which provides SAP applications with a standardized way ofexecuting and managing condition based business tasks.The output management adapter has following capabilities: PPF utilities:oTechnical connection between the PPF action profiles and BO nodesoGenerates PPF triggers for BO node instancesoProcesses triggers in two modes depending upon the configuration settings –“before commit” and “after commit”. These enable the user to segregate criticaland non-critical actions.BO to wrap PPF transaction data that facilitates:oOutput management UIoPreview of output for individual unprocessed triggers (PDFs, alert data, and soon)oRead from archive and preview for processed triggersoRepeat of a trigger (it currently checks the merging constraints as set in the PPFconfiguration if required)oManual generation of triggers (this currently checks for the scheduling andmerging constraints set in the PPF configuration)Basic output management features are described below in more detail. SAP AG13

3.1 Immediate PrintYou can manually trigger a print action directly from the document. This is a forceful execution ofthe output regardless of the schedule conditions and start conditions. The schedule conditionsand start conditions are ignored and the document is printed. An immediate print is not recordedin the archive.If you choose Print Immediately, the system displays a dialog box that lists all of the actions thatare relevant for external communication. It also displays a switch option that allows you to choosebetween the output details (output device and number of copies) pertaining to the user or the PPFconfiguration.You must create a BOPF action in the root node of the BO and assign the name/BOFU/S PPF IMMEDIATE PRINT to the parameter structure. Class/BOFU/CL A PPF IMMEDIATE PRINT, which contains the implementation steps for theimmediate print function, must also be provided.You can enter the information about the default printer and the number of copies in the followinglocations: User profile Condition configuration in the PPFBy default, the settings in the user profile are taken into consideration. If the BO is to use thevalues from the condition configuration instead, they must inherit the immediate print class andthe value in the constructor must be set using constant MC CONDITION DEVICE for the variableMV PRINT SETTINGS.Note: An alternative way of triggering an immediate print is to set the processing time parameterin Customizing for the action definition to Processing Using Selection Report. The action is thenscheduled but not executed. You can then execute the action manually from the outputmanagement UI.The current filtering logic removes all non-print PPF actions (such as Send B2B message). SAP AG14

3.2 Automated OutputYou can schedule automated outputs throughout the life cycle of a business document. Outputsare scheduled and executed on the basis of the business scenarios and the life cycle status.Some of the configured action definitions are not relevant for a business document in a specificbusiness scenario. The relevant actions and outputs are included using the schedule conditions.These outputs could be partner-dependent or partner-independent. For partner-dependentactions, the business object provides the partner-specific data and outputs are triggered on thebasis of this data (you can change or override some of the parameters on the outputmanagement UI prior to execution). Automated outputs are saved in the history and can beviewed on the Output Management tab page.If you want to e-mail external communication, you can send attachments along with the e-mail.Attachments can be added from the following locations: Customizing settings for the PPF Output management UIThe output management UI is supplied with a list of attachments. These attachments areadded as part of the attachments folder UI.If you want to print external communication, there are various ways in which you can specify theprinter. The printer is determined in the following order of priority:1. Redefining method DETERMINE PRINTER( ) of class /BOFU/CL PPF SERV FOR BO.The printer can be determined using ABAP or BRFplus.2. The static configuration setting in Customizing for the PPF3. User Printer setting SAP AG15

3.3 Originals and CopiesThe output management adapter does not differentiate between originals and copies of businessdocuments. The print form is also the same for both originals and copies. The difference isbrought about by configuring different actions for originals and copies. The originals and copiesare printed in different trays of the same printer, which contain different types of paper. Thesetrays can be modeled as two separate SAP printer configurations. For more information, see SAPNote 143375.This is relevant only for external communication. SAP AG16

3.4 Mass OutputYou can trigger mass outputs from a worklist. For example, you can select multiple orders fromthe worklist, choose the actions for which you want to trigger the mass outputs, and then performmass execution of the unprocessed actions. The system checks the start conditions and if theoutcome is successful, the actions are executed.You have to create a BOPF action in the root node of the BO and provide class/BOFU/CL A PPF MASS OUTPUT, which contains the implementation measures for the massoutput function. SAP AG17

3.5 Features of the Output Management UIThe header area of the output management user interface (UI) uses a table to display all of theactions for a business document. The system displays the action details, message log,communication details, and document preview on separate tab pages in the screen area belowthe table. Depending on the processing status, the system groups the actions as Unprocessed,Successfully Processed, or Processed with Errors.Generate ActionsYou can generate all of the relevant actions for a business document. If you chooseActions Including Conditions Checks , the system performs the following tasks: Selects all of the relevant actions for the business document Executes the schedule conditions Generates the actions if the schedule conditions are metGenerateThe system executes the actions either immediately or when you save, depending on how youhave configured the action. In the Maintain PPF Settings Customizing activity, you can set theProcessing Time field to Immediate processing, Processing when saving document, orProcessing using selection report. If you validate changes to data in the scheduled condition todetermine whether you create a new trigger, you may not be able to generate the triggermanually. This is because the data in the business document has not been changed since thelast trigger was generated. You can validate changes to data in the scheduled condition bycomparing the data before and after the change.In the Maintain PPF Settings Customizing activity, if you specify an action as ScheduleAutomatically and the processing time as Processing when saving document, the systemgenerates a trigger in the active state in the UI and deletes the trigger on saving.However, the system does not delete the trigger if the trigger is changed.List of ActionsYou can view the list of all actions that are relevant for the document by choosing GenerateList of Actions . A dialog box appears with the list of all the possible actions for the document,along with the configured processing types, and schedule condition status. You can view thelatest status of the schedule condition by choosing Check Schedule Conditions. You can selectone or more actions for generation. You can generate the actions by choosing the GenerateActions pushbutton and choosing one of the following options: Include Condition checksYou can generate the selected action after executing the relevant schedule conditions. Ifthe schedule conditions are met, the actions are generated. Skip Condition ChecksYou can generate the selected actions without checking the relevant schedule conditions.The system always generates the actions, regardless of whether or not the scheduleconditions are met. You can specify which actions can be generated without checking the SAP AG18

schedule conditions in the Maintain Output Management Adapter Settings Customizingactivity.Generating an action without checking the schedule conditions may lead topossible inconsistencies in the document. We do not recommend that you dothis. To restrict the actions that can be generated in this manner, you can selectthe actions that are safe to generate without schedule condition checks in theaction settings of the Maintain Output Management Adapter SettingsCustomizing activity. Unless specified otherwise in Customizing, the systemexecutes actions only if the schedule conditions are met.The system merges generated actions, based on the merging method youspecify for the action definition in the Maintain PPF Settings Customizing activity.RegenerateYou can regenerate specific actions by selecting existing processed actions on the OutputManagement tab page and choosing Regenerate. The system evaluates the schedule conditionsand generates the action on the basis of the evaluation. You can use the Regenerate functiononly for actions with a processing type of External Communication.EditThe ability to edit in output management is influenced directly by the lock status of the consumingbusiness object (BO). If the BO is in display mode, then the output management UI is also indisplay mode.You can edit all of the unprocessed actions. This enables you to enter or change the data inspecific fields for all of the unprocessed actions. This function is only possible for the actions witha processing type of External Communication.You can change the following fields for an unprocessed action: LanguageIf you schedule actions for execution when you save a business document, theconsuming application can determine the language based on the business partner. Thesystem displays the language on the Outputs tab page. If you want to repeat the action ata later time but in a different language, you can change the language on the UI andexecute the output. This function is only possible for the actions with a processing type ofExternal Communication. PrinterYou can change the printer. Number of Print CopiesYou can enter the number of copies to be printed. This should be a value between 1 and255. Subject and Text SAP AG19

oBy default, the system uses the description of an action as the subject for anunprocessed trigger.oYou can use the Maintain Output Management Adapter Settings Customizingactivity to create a default e-mail text.RecipientsYou can add, change, and delete the recipient types and recipients for externalcommunication. AttachmentsYou can attach or delete attachments that you send to e-mail recipients. Interactive PDF contentYou can edit the content of an interactive PDF form for an unprocessed action. Deactivate an actionYou can deactivate an action if you do not want to execute the action in a particularscenario.Subject and TextYou can send business documents to e-mail recipients. By default, the system uses the subject of an unprocessed trigger as the descriptionfor an action. You can use the Maintain Output Management Adapter Settings Customizing activityto create a default e-mail text.RecipientYou can add and delete recipients of external communication triggers. The system supports thefollowing recipient types: E-mail Fax Business partner SAP name If the system can determine the communication mode preferences for a businesspartner, it displays this automatically. For an action, it is not possible to specify a mode of communication by businesspartner. SAP AG20

Editing Interactive PDF contentYou can associate an interactive PDF with an action, and edit the PDF. You can save thechanged document, and change the document later if required. In the Maintain PPF Settings Customizing activity, you can specify that the systemarchives a PDF on execution. The system supports the interactive feature for PDF forms only with template typeZCI.AttachmentsYou can attach or delete attachments that you send to e-mail recipients with a businessdocument. You can add attachments that you have specified in the following places: Maintain PPF Settings Customizing activity BAdI Attachments folder of the consuming BODue to technical limitations the system writes the addition or deletion of an attachment to thedatabase records. This means that even if you exit the consuming application without anexplicit save, the system keeps

the business object. The persistence of this object must be realized using the object services. Business object Object that contains the main data that is relevant for action determination and execution. Its persistence is either given as a Business Object Repository (BOR) object or as a persistent class of the object services.

Related Documents:

Cisco 3560 & 3750 NetFlow Configuration Guide Cisco Nexus 7000 NetFlow Configuration Cisco Nexus 1000v NetFlow Configuration Cisco ASR 9000 NetFlow Configuration Appendix. 3 Cisco NetFlow Configuration Cisco IOS NetFlow Configuration Guide Netflow Configuration In configuration mode issue the following to enable NetFlow Export:

3. Layer 2 - LAN Switching Configuration Guide 4. Layer 3 - IP Services Configuration Guide 5. Layer 3 - IP Routing Configuration Guide 6. IP Multicast Configuration Guide 7. ACL and QoS Configuration Guide 8. Security Configuration Guide . IP network IRF virtual device IP network IRF link Equal to Master Slave Basic Concepts Role

Configuration Management For Dummies consists of five chapters that explore the following: » The basics of configuration management (Chapter 1) » Configuration management use cases (Chapter 2) » How to build a configuration management database (Chapter 3) » How to maintain a configuration management database (Chapter 4) » Key milestones on your .

Configuration Management (CM): The systematic evaluation, co-ordination, review, approval or disapproval, documentation and implementation of all proposed changes in the configuration of a product, after formal establishment of its configuration baseline. Configuration Items (CI): Configuration items are the basic units of configuration management.

Paper output cover is open. [1202] E06 --- Paper output cover is open. Close the paper output cover. - Close the paper output cover. Paper output tray is closed. [1250] E17 --- Paper output tray is closed. Open the paper output tray. - Open the paper output tray. Paper jam. [1300] Paper jam in the front tray. [1303] Paper jam in automatic .

Contents iv Cisco IOS XR Command Modes Reference HSRP Interface Configuration Mode CMR-6 Interface Address Family Configuration Mode CMR-7 Interface Configuration Mode CMR-7 Interface Configuration Mode (Protocol Areas) CMR-8 Interface IGMP Configuration Mode CMR-8 Interface Management Configuration Mode CMR-8 Interface Mulitcasting Mode CMR-9 Interface PIM Configuration Mode CMR-9

Cisco 3560 & 3750 NetFlow Configuration Guide Cisco Nexus 7000 NetFlow Configuration Cisco Nexus 1000v NetFlow Configuration Cisco ASR 9000 NetFlow Configuration Appendix. 8 Cisco NetFlow Configuration Cisco 3560X & 3750X NetFlow Configuration Your software release may not support all the features documented in this module.File Size: 2MB

To determine the electron configuration of any of the first 38 elements of the periodic table To determine the identity of an element from its electron configuration To complete an orbital diagram using arrows to represent electrons . . rows on the periodic table .File Size: 863KBPage Count: 31Explore furtherElectron Configuration Chart for All Elements in the .sciencestruck.comElectron configuration of every element in the periodic tablewww.biochemhelp.comElectron Configuration Chart - ThoughtCowww.thoughtco.comList of Electron Configurations of Elementssciencenotes.orgElectron Configuration - Detailed Explanation with Examplesbyjus.comRecommended to you based on what's popular Feedback