SAP ABAP: ABAP WORK FLOW SCENARIOS IN MM ERP,My SAP,ABAP,FICO,CRM,BW

Showing posts with label ABAP WORK FLOW SCENARIOS IN MM. Show all posts

ABAP Programming for Material Documents for MM Module

Programming with sap abap report lists the material documents that posted for one or more materials. The report’s drill down capacity allows you to view all supporting documents. Material documents are posted with all goods movements, including those in which stock does not actually move (for example, a change in batch number for a material). Material documents are posted from transactions such as purchase order receipts, issuing components to production orders, and the “post goods issue”for a delivery on a sales order.

No prerequisites are required to run this report. However, you should limit the selection criteria to restrict the material document listing. The Setting checkboxes allow you to select different ways the output can be shown at the bottom of the selection screen .

This report generates information that can be used to find all the production order1 receipts for a set of materials in a given time period. For example, you can find all the movements of a particular material batch (lot) within a quarter. From the list, you can select (and view) any of the listed material documents. In addition to viewing a material, you can view the total stock quantities (stock overview) for the material.

This report contains data obtained from material documents and material information. As such, the data cannot be changed or manipulated from the report.

To access the first screen for this report, choose Logistics → Materials management → Inventory management → Environment → List displays → Mat.doc.for material.

1. Enter 3000 in Plant.
2. Enter 101 in Movement type.
3. Enter a date range in Posting date (for example, 01/01/1997 to 12/31/1997).
4. Choose Execute.

This screen shows a listing of material document line items arranged by material. In this example, if you scroll down to material P-100, you find two receipts made on two separate documents.

sap sales order programming report

sap sales and distribution back orders report in abap
sap sales and distribution incoming order report
sales in erp programming invoice report
sap abap programming in mm module report about purchase order

WORK FLOW FOR SD COMPLETE

EDI
BAPI
BADI
ALE IDOC
SAP Work Flow
SAP Work Flow in Sales and Distribution
SAP Work Flow in Material Management
ERP Overview
My SAP
SAP CRM

Work Flow
Work Flow MM
Work Flow SD
Communication Interface
MySAP CRM Customer Relationship Management
MySAP Best ERP

SAP ABAP WORK FLOW FOR MM

Learn SAP ABAP work flow for materiel management module here at the following posts.

Work flow for MM PART 1

Work flow for MM PART 2

Work flow for MM PART 3

Work flow for MM PART 4

Work flow for MM PART 5

Work flow for MM PART 6

Work flow for MM PART 7

Work flow for MM PART 8

Work flow for MM PART 9

Work flow for MM PART 10

Work flow for MM PART 11

ABAP TOPIC WISE COMPLETE COURSE

ABAP 51 Days Complete Course
ABAP Dictionary
OOPS in ABAP
BDC
SAP Scripts
SAP Scripts Controls
SAP Smart Forms
Real Time ABAP Programming Reports
SAP Interview Questions
Syntax for ABAP Programming
ABAP Interface Programming
Financial and Controlling Sample Reports

EDI
BAPI
BADI
ALE IDOC
SAP Work Flow
SAP Work Flow in Sales and Distribution
SAP Work Flow in Material Management
ERP Overview
My SAP
SAP CRM

Work Flow Scenarios in Material Management of SAP ABAP Part Eleven

Extending Arrangements in Purchasing (MM-PUR-VM)

Arrangements are defined for a fixed period (such as a year), and are settled at the end of this period. Arrangements that are to be valid for longer periods (such as longer than a year) can be extended, if an arrangement calendar exists for them.

An arrangement must be extended before the relevant purchasing documents (such as purchase orders) are entered, if the price determination date for these documents falls within the validity period of the new (that is, extended) arrangement.Process Flow The staff in Purchasing who agreed the arrangements can be sent a message on the extension dates set in advance via workflow.This means that, on the extension dates, a work item is sent to their inbox which they can use to call the extension transaction and relevant arrangement.Compared to extension of arrangements by mass processing (transactions MEB7 and MER7),workflow processing has the added advantage of allowing you to change the currency of the arrangements. This is not possible in “Change” mode.

Technical Implementation (MM-PUR-VM)

Object Types Used
Object technology is used to create the interface between the R/3 functions and the

workflow system. The information given below is of a technical nature and is not necessary for an initial overview.

Standard Tasks

The standard tasks provided by SAP as single steps describe the basic business activities from an organizational point of view. A single-step task relates to a single object method (= technical link to R/3 functionality), and is linked to the agents possible from an organizational point of view.

Object: Volume-Rebate Arrangements in Purchasing

(MM-PUR-VM) Definition

A volume-rebate arrangement in Purchasing is a volume-rebate arrangement that a purchasing organization agrees with a vendor (condition granter).Use In this scenario, a volume-rebate arrangement in Purchasing is extended.Location in object repository: Materials Management _ Purchasing _ Vendor - Material Relationships and Conditions .

Standard Task TS24500005: Extending Volume Rebate

Arrangements in Purchasing (MM-PUR-VM)

Use

In this standard task, an arrangement in Purchasing is extended.Object method referenced: object type BUS3030 (volume rebate arrangement - Purchasing), method: EXTENDMANUALLYWITHMODIFICATION (extend manually).Agent assignment: For the validity period, this standard task is addressed to the agent(s) in the purchasing group which is responsible for the arrangement. You must make the following settings in Customizing for this:

Assign the purchasing groups responsible to the required organizational units or organizational management positions.Triggering events of the task The event ToBeExtendedManually has been entered as the trigger for object type BUS3030 (rebate arrangement in Purchasing).

This link between the event and the workflow template to be started is normally inactive in the standard system. If the workflow template is to be started, it must first be activated in the Customizing application for the SAP Business Workflow.Task container and binding The object reference to the rebate arrangement in Purchasing exists as event parameters in the container of the triggering event and must be transferred to the workflow container via a binding.

The standard system includes the following binding definition between the triggering event and the workflow container:
Workflow Container Event Parameter Container
RebateAgreementPur _Evt_Object

Steps in a Workflow

Workflow can be started for all arrangements to be extended by means of a report (Material management _ Purchasing _ Master data _ Subseq. settlement _ Arrangement settlement _ Extend __Via workflow).

Events are created for the selected arrangements, and these events trigger generation of work items for extension.Separate workflow is started for each extension for each individual arrangement. This work item is sent to the purchasing group responsible. During extension, it is possible to change the arrangement currency. By this stage, it is not possible to do this in transaction MEB2 (change arrangement).

Preparation and Customizing (MM-PUR-VM)

In addition to general customizing, which ensures that the workflow system functions correctly, customizing is also required specifically for this workflow template.

Activities Processing the organizational structure

An arrangement in Purchasing is always settled by the purchasing group responsible. All purchasing groups which extend arrangements using workflow must therefore firstly be entered in Customizing for SAP Business Workflow. A purchasing group is usually assigned to an organizational unit. An organizational unit is an area of a company, e.g. a department.

Enter your organizational plan by choosing Customizing activity Basis Components _ Business Management _ SAP Business Workflow _ Edit organizational plan.Execute Customizing activity Basis Components _ Business Management _ SAP Business Workflow _ Basic Settings _ Maintain assignments for SAP organizational object types, and assign the purchasing groups to the organizational units or positions which the purchasing groups represent (object type T024).

Performing Task-Specific Customizing

You assign tasks in Material Management as follows:

1. Execute the Customizing activity (Basis _ Business Management _ SAP Business Workflow _ Perform task-specific Customizing.

2. Choose Materials Management _ Purchasing _ Vendor - Material Relationships and Conditions and choose activity Assign tasks to agent.

3. Classify standard task TS24500005 (extending volume-rebate arrangements in Purchasing) as a general task.

Activate Event-Receiver Linkage

The event ToBeExtendedManually for object type BUS3030 (volume rebate arrangement -Purchasing) is a triggering events of workflow template 24500005 (extending volume rebate arrangements in Purchasing) and is entered as standard in the event coupling table. So that the event is actually started, the linkage between the triggering events and the task, as the receiver of the event, must be activated in SAP Business Workflow Customizing.

Activate the task MMArrangExt in your system as follows:

1. Execute the Customizing activity Basis Components _ Business Management _ SAP Business Workflow _ Perform task-specific Customizing.

2. Activate event coupling for the workflow template (Materials Management _ Purchasing _ Vendor - Material Relationships and Conditions _ Activate event coupling).

Operation and Connection with Application

Functionality (MM-PUR-VM)

Agreed arrangements in Purchasing, which have an arrangement calendar, can be transferred for extension to Business Workflow at regular intervals. The ways of doing this are described below. These measures should be carried out by a coordinator (e.g. a central coordinator or a coordinator for the individual purchasing organization):

1. The coordinator uses the report offered under Material management _ Purchasing _Master data _ Subseq. settlement _ Arrangement _ Extend _Via workflow to manually select the arrangements and start the single-step tasks in good time before the end of the validity period. Each arrangement can only be extended once.

2. If you need to start the report for extending arrangements using workflow at regular intervals (e.g. each week), you are advised to execute this report in the background. This involves two steps:

a) First you must define suitable variants for this report (report name: RWEWU001), in which the extension date is defined as a selection variable, and is filled with the day’s date each day. You can also add other selection criteria as required.
b) Then plan for the report to be executed in the background at the intervals you
require.

VMI: Creating and Acknowledging a Purchase Order From IDoc ORDRSP VMI (MM-CBP)

Purpose

Workflow is used to create and simultaneously acknowledge a purchase order during the inbound processing of IDocs of message type ORDRSP with message variant VMI. The IDoc may be sent by your vendor, for example, if the vendor wants to supply you with goods using Vendor Managed Inventory (VMI).

VMI enables a vendor to offer your company the service of planning requirements of the vendor's articles.Process Flow Workflow is started if a vendor wants to create a purchase order by EDI in your system as part of a VMI scenario.As a result, an IDoc is transferred and used to generate and acknowledge the purchase order in your system.The purchase order is usually created and acknowledged completely in the background. Work items are only created if errors occurred. These work items are displayed in the integrated inboxes of the people responsible for processing the errors.
Once a work item is executed, automatic checks are carried out again. If no further errors occur, workflow is complete.

Technical Implementation (MM-IV-CBP)

The following information is of a technical nature. You need the information if you are interested in the details of implementation, or want to carry out enhancements yourself.

Object Types

Object technology is used to create the interface between the SAP functions and the Workflow system.The methods and events used to trigger workflow and to process the work items are provided by object type IDOCORDRSP (IDoc message ORDRSP). This object type represents the purely technical interface for executing work items, not a concrete IDoc.Task Group Task groups are collections of standard tasks, workflow templates and other task groups that are used in the same context.The workflow described here is assigned to task group 20000011.

Preparation and Customizing (MM-PUR-CBP)

Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.

Operation and Link to Application (MM-CBP)

Workflow is automatically triggered by IDoc inbound processing (process code ORDV) if a vendor wants to create a purchase order by EDI in your system as part of a VMI scenario. In this process, an IDoc of type ORDRSP and message variant VMI is sent to your SAP system. This results in a purchase order being created in the background.If errors occur, work items are created and sent to the integrated inboxes of the people responsible for processing the errors. Errors may arise as a result of missing master or Customizing data in the SAP System, or incorrect/insufficient data in the IDoc.

The people responsible can display the IDoc from the work items, and then change or add to the data, or make changes in the article master or in Customizing, as required. The people responsible can trigger inbound processing directly from the work item, or flag the IDoc for deletion.If inbound processing is triggered, the whole process is carried out again. If the system does not find any further errors, a purchase order is automatically generated and acknowledged.If errors occur during the acknowledgement of the purchase order, work items are created. The people responsible for processing the errors can display the IDoc directly from the work items and analyze the errors. In this case, however, error handling directly from the item is not possible. The standard IDoc tools must be used to process the errors.

If the system finds no further errors after the work items have been executed, workflow is complete.

RELATED POSTS

ABAP WORK FLOW PART ONE
Mysap web application server
SAP web application and business server pages

Work Flow Scenarios in Material Management of SAP ABAP Part Ten

Parking: Complete Invoices for Posting

In Logistics Invoice Verification, you can park invoices, credit memos, subsequent debits, and subsequent credits in the Document Parking function. If different groups of processors are to park invoice documents and complete them for posting, you can implement this workflow.All users that are authorized to complete parked documents for posting, receive a work item in their inbox. They can change parked documents using this work item. The work item appears in these employees’ inbox until the parked document has been completed for posting or the invoice document is completed for posting, deleted, or posted outside the workflow.The workflow ends when a user in the group of processors who complete documents for posting does one of the following with the invoice document:

Saves it as complete

Deletes it

Posts it

Technical Implementation (MM-IV-LIV)

Object technology is used to create the interface between the R/3 functions and the Workflow system. The information given below is primarily of a technical nature and is not necessary for an initial overview.

Workflow Template

The actual operational procedure is implemented as a workflow template. You will find this workflow template in your R/3 System.

Workflow template: WS 20001003

Description:

Complete the Parked Log. IV Document Triggering Event for Workflow TemplateThe workflow template is triggered by the event IncomingInvoice.parked, if the invoice document is parked (parked status: RBKP-RBSTAT='A'), or if the invoice document that was complete for posting is changed and only parked afterwards.This coupling between the event and the workflow template to be started is deactivated in the standard system.

If you want to use the workflow template, you have to activate it in Customizing for Logistics Invoice Verification.For more information, see Preparation and Customizing (MM-IV-LIV).User Roles Invoice documents that have been completed for posting are saved at the following organizational levels:

Processor Determination: Clerk Responsible for Completing Invoices for Posting If you have already maintained an organizational unit, you can use it here.If no organization unit is available, create an organizational unit that includes the people responsible for completing parked invoice documents for posting.Link the organizational unit to the single-step task TS20000878:

By simple processor assignment

All users in the organizational unit receive the work item.

By defining a single role

Only selected users in the organizational unit receive the work item.

Preparation and Customizing (MM-IV-LIV)

Authorization Objects

You must have maintained authorization to change parked invoice documents (activity 77, M_RECH_WRK) for users who are to complete parked invoice documents for posting.Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.

Performing Task-Specific Customizing

List here all the organizational management objects and classify the general tasks.Activating Event-Receiver Linkage The event IncomingInvoice.parked (Invoice parked) for object type BUS2081 (Incoming invoice) is an event that triggers workflow template WS 20001003 and is entered in the event linkage table as such as the standard event.

This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you activate the linkage between the triggering event and the workflow template as receiver of the event in Customizing for Logistics Invoice Verification. (Logistics Invoice Verification _ Document Parking _ Activate Workflow Template for Document Completion.)

Link to the Application (MM-IV-LIV)

The accounts payable clerk receives a work item in his or her inbox. He or she can change parked invoice documents using this work item.For example, a parked invoice document still contains a balance. Once the invoice document has been changed, the balance should be zero and the system can post the invoice document if necessary.

If the invoice documents are also subject to a release procedure and you implement the workflow Release of Invoice Documents Completed for Posting, the accounts payable clerk should save the invoice documents as complete.

Parking: Release of Invoices Completed for Posting (MM-IV-LIV)

You can use a workflow to control the process flow of document parking in Logistics Invoice Verification. You implement this workflow if invoice documents have to be approved by certain users before posting if they exceed certain release criteria.During the release procedure, the person responsible for releasing the invoice document decides if it should be released. If he or she decides to release the document, it is first released in the background and then posted.

If he or she rejects the invoice document release, the document is forwarded with a memo containing the rejection reason to the accounts payable clerk responsible for completing documents for posting so that he or she can change it.When the invoice document has been saved as complete and is subject to release, the person responsible for releasing it again receives a work item for processing in his or her inbox.The workflow ends when the person responsible for releasing the invoice document does one of the following things:

Releases it

Posts it

Deletes it

Prerequisites

In the Implementation Guide (IMG) for Logistics Invoice Verification, you can specify for which company code, which vendors, which invoices, and above which amount a document is subject to release. In an invoice document that is completed for posting, the amount that is subject to release is based on the gross amount. (Logistics Invoice Verification _ Document Parking _ Define Release Criteria)

Technical Implementation (MM-IV-LIV)

Object Types

Incoming invoice

Object type Bus2081 (Incoming invoice)

Workflow Template

The actual operational procedure is implemented as a workflow template. You will find this workflow template in your R/3 System.

Workflow template: WS 20001004

Description: Release the Completed Log. IV Document

Triggering Event for Workflow Template

The event for workflow template IncomingInvoice.CompletedToRelease is triggered if the parked document is complete for posting (RBKP-RBSTAT='B') and is subject to release (RBKPRFGKZ=' X').This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you have to activate it in Customizing for Logistics Invoice Verification.User Roles You complete parked invoices for posting and release them at the following organizational levels.

Processor Determination: Clerk Responsible for Releasing Invoices

If you have already maintained an organizational unit, you can use it here.If no organization unit is available, create an organizational unit that includes the people responsible for releasing invoice documents that are complete for posting.Use the organizational unit in Customizing for Logistics Invoice Verification in the activity for defining release criteria.

Preparation and Customizing (MM-IV-LIV)

Authorization Objects

You must have maintained the authorization to display invoices (activity 03,M_RECH_WRK) for users who are responsible for releasing invoices.You must have maintained authorization to change parked invoice documents (activity 77, M_RECH_WRK) for users who are to complete parked invoice documents for posting.Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.

Performing Task-Specific Customizing

List here all the organizational management objects and classify the general tasks.This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you activate the linkage between the triggering event and the workflow template as receiver of the event in Customizing for Logistics Invoice Verification. (Logistics Invoice Verification _ Document Parking _ Activate Workflow Template for Release for Posting.)

Link to the Application (MM-IV-LIV)

The release of invoice documents that have been completed for posting is supported by a link to a workflow procedure.

Prerequisites

The event IncomingInvoice.CompletedToRelease must be triggered for an invoice (BUS2081) so that a release procedure is started. We recommend implementing this workflow together with the SAP workflow template WS20001003.In Customizing for Logistics Invoice Verification, you maintain the activity Define Release Criteria under Document Parking.

Features

Release for Posting

In the release step, the person responsible for releasing the invoice document decides if it should be released. The system uses the virtual attribute ReleaseAgent for object type BUS2081 to determine the person responsible for releasing the document. The release criteria in Customizing for Logistics Invoice Verification are checked for this.If the person responsible decides to release the document, it is first released in the background and then posted.

If he or she decided to reject the document, it is forwarded for further processing to the accounts payable clerk responsible for completing invoice documents for posting. The rejection reason should have been entered using the memo function.Completing Invoices for Posting The accounts payable receives a work item in his or her inbox. In this work item, he or she can read the reason why the invoice document was rejected and change it.

If the accounts payable clerk parks the changed invoice document, saves it as complete, deletes it, or posts it, the workflow ends. It makes sense to save the invoice document as complete and therefore trigger the release workflow again, assuming that the invoice document is subject to release.If the invoice document is parked, deleted, posted, or released in the background outside the workflow process, the workflow ends.

WORK FLOW IN MM PART 11

SAP Authorization and ALE

SAP security authentication and authorization

Work Flow Scenarios in Material Management of SAP ABAP Part Nine

Preparation and Customizing

Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.

ActivitiesDefining the Organizational Structure

In Purchasing, settlement accounting with respect to a rebate arrangement is always carried out by the responsible purchasing group. All purchasing groups that have to carry out settlement accounting via workflow must therefore first be identified in Customizing for SAP Business Workflow. A purchasing group is typically assigned to an organizational unit. Organizational units are a means of subdividing an enterprise according to various business criteria (for example, most enterprises are made up of different departments).

Define your organizational structure via the Customizing activity (Basis Components _ Business Management _ SAP Business Workflow) _ Edit organizational plan.Perform the Customizing activity (Basis Components _ Business Management _ SAP Business Workflow _ Basic Settings) _ Maintain Assignments for SAP Organizational Object Types, and assign the purchasing groups (object type T024) to the organizational units or positions that the purchasing groups represent.

Performing Task-Specific Customizing

Here you list all organizational management objects (e.g. jobs or positions) that are generally allowed to carry out settlement accounting with regard to rebate arrangements in Purchasing and classify the general tasks.

You assign tasks in Materials

1. Perform the customizing activity (Basis Components _ Business Management _ SAP Business Workflow _) Perform Task-Specific Customizing.

2. Then, under Materials Management _ Purchasing _ Vendor - Material Relationships and Conditions, choose the activity Assign Tasks to Agent (processor).

3. Classify the standard tasks TS00900055 (Comparison of Business Volumes for Rebate Arrangement), and TS00900058 (Settlement Accounting for Rebate Arrangement) as general tasks.

Activating Event-Receiver Linkage

The events ToBeSettledInterim (for partial settlement accounting) and ToBeSettledFinal (for final settlement accounting) for the object type BUS3030 (rebate arrangement - Purchasing) are triggering events of workflow template 00900007 (settlement accounting with regard to rebate arrangements in Purchasing) and are entered as such in the event linkage table in the standard system. For the workflow template to actually be started, the linkage between the triggering events and the workflow template as receiver of the events must be activated in Customizing for
SAP Business Workflow.

Preparation and Customizing (MM-PUR-VM)

Activate the workflow template MMRebAgSettl in your system as follows:

1. Perform the customizing activity (Basis Components _ Business Management _ SAP Business Workflow _ Basic Settings) _ Perform Task-Specific Customizing.

2. Activate event linkage for the workflow template (Materials Management _ Purchasing _ Vendor - Material Relationships and Conditions _ Activate Event Linkage).

(Alternatively, you can activate event-receiver linkage by processing the workflow template directly.)

Operation and Link to Application (MM-PUR-VM)

Rebate arrangements entered into with vendors by Purchasing can be passed on to Business Workflow for settlement accounting purposes at regular intervals. There are two possible ways of doing this, both of which should be carried out by a person acting as a coordinator. The latter can be a central coordinator or a coordinator for a particular purchasing organization.

Activities

Manuel execution

The coordinator regularly carries out settlement accounting with regard to rebate
arrangements via Settlement acctg. _ Via workflow.

Automatic periodic execution

Since the program for settlement accounting via workflow should be run regularly (e.g. each week), it is advisable to execute this program in the background at the desired intervals. This involves two steps:

a) First define suitable variants of the program (program name: RWMBON11), in which the settlement date field is defined as a selection variable and dynamically filled with the current date. You can also add other selection criteria as required.

b) You then schedule the program to be run in the background with a desired period. See the documentation on background processing: BC Computing Center Management
System _ Background Processing _ Scheduling and Managing Background Jobs.

Release of Invoices Blocked for Price Reasons (MM-IVLIV)

In Logistics Invoice Verification, invoice items are blocked due to price variances. Financial Accounting cannot pay these invoices.If a price block is defined for invoice items, the system can inform the buyer responsible for the purchase order automatically via workflow. This means that he or she sees a work item in his or her inbox, which he or she can use to verify the blocked invoice items and then process them as follows:

Change the purchase orders
Release the invoice items by deleting the blocking reason
Flag the invoice items as cannot be clarified

The workflow ends when the price blocks in the invoice items are no longer valid because the order prices have been changed, or when the invoice item is released because the blocking reasons have been deleted.If you flag price blocks in the invoice items as cannot be clarified, the system creates a work item for the accounts payable clerk. The accounts payable clerk then explicitly ends the workflow.

Technical Implementation (MM-IV-LIV)

Object Types

Object technology is used to create the interface between the R/3 functions and the Workflow system. The information given below is primarily of a technical nature and is not necessary for an initial overview:

Incoming invoice

Object type Bus2081 (Incoming invoice)
Workflow Template

The actual operational procedure is implemented as a workflow template. You will find this workflow template in your R/3 System.
Workflow template: WS 20000397
Description: Handling invoices blocked due to price

Triggering Event for Workflow Template

This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you have to activate it in Customizing for Logistics Invoice Verification.

User Roles

You check and release invoice items that are blocked for price reasons at the following organizational levels. The processor is also determined at these levels.

Processor Determination: Buyer

If you have already maintained an organizational plan, you can use it here.If there is no organizational plan, you need to create a Purchasing department. For each purchasing group, you define a position and link it to the entries in table T024. You define the users for each position.

Processor Determination: Accounts Payable ClerkIf you have already maintained an organizational unit, you can use it here.If there is no organizational unit, you need to create the organizational unit Invoice Verification.Link the organizational unit to the single-step task TS20000704:

By simple processor assignment

All users in the organizational unit Invoice Verification receive the work item.

By defining a specific role

Only selected accounts payable clerks receive the work item. For example, you can use the attribute User name, which contains the accounts payable clerk’s name.Note that a standard user group for invoices that are posted in the background is stored in the role.

Preparation and Customizing (MM-IV-LIV)

Authorization Objects

You need to maintain the following authorizations for the buyers who release invoice items blocked due to price:

Authorization to display (activity 03) and change (activity 02) purchase orders M_BEST_BSA, M_BEST_EKG, M_BEST_EKO, M_BEST_WRK

Authorization to display invoices
M_RECH_WRK

Authorization to delete (change the invoice) the blocking reason Price (activity 02)
M_RECH_EKG Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.

Defining the Organizational Structure

Various buyers can check and release invoice items that are blocked due to price. You need to identify them all in Customizing for SAP Business Workflow. These buyers can be assigned to various organizational units. Organizational units are a means of subdividing an enterprise according to various business criteria, such as purchasing groups.For each purchasing group, you define a position and link it to the entries in table T024. You define the users for each position.

Performing Task-Specific Customizing

Here you list all organizational management objects that are generally allowed to release invoices blocked for price reasons (such as purchasing groups) and classify the general tasks.

Activating Event-Receiver Linkage

The event IncomingInvoice.blockedPrice (Invoice item blocked due to price variance) for object type BUS2081 (Incoming invoice) is an event that triggers workflow template WS 20000397 and is entered in the event linkage table as such as the standard event.This coupling between the event and the workflow template to be started is deactivated in the standard system. If you want to use the workflow template, you activate the linkage between the triggering event and the workflow template as receiver of the event in Customizing for Logistics Invoice Verification. (Logistics Invoice Verification _ Invoice Block _ Activate Workflow Template)

Link to the Application (MM-IV-LIV)

The buyer should check whether the price variance in an invoice item is justified. The buyer can make use of the following environment information for the invoice items: invoice, purchase order, and memos.He or she can process the invoice items and the purchase order items that they are based on as follows:

Change purchase order

Release invoice item

Flag invoice item as cannot be clarified

Prerequisites

The event for the change document Purchase Order.changed must be triggered for the purchase order (BUS2012) so that you can change a purchase order.Features Change Purchase Order The buyer can change the relevant purchase order for selected invoice items blocked for price reasons. If all the purchase orders have been changed, the system checks if the price blocks in the invoice items have become invalid due to the change in the order prices. If this is the case, the system deletes the blocks and releases the invoice for payment.If there are still price blocks that need to be clarified, the buyer can process the work item again.

Due to technical restrictions, the system does not advance in online mode after calling the transaction Change Purchase Order. You must call the work item Further processing Invoice in the integrated inbox. This additional call of the work item does not apply to later releases.

Release Invoice Item

You can delete the blocking reasons for blocked invoice items. The system checks if the buyer has authorization to delete the blocking reason for the items selected. If this is the case, the system releases the invoice items blocked for price reasons and they can be paid.If there are still price blocks that need to be clarified, the buyer can process the work item again.

Flag Invoice Item as Cannot Be Clarified

The buyer uses the memo function on the invoice display to document selected invoice items flagged as cannot be clarified. To do this, choose System _ Links, then choose Create note on the invoice display screen.The system saves the price blocks that are flagged as cannot be clarified. If there are still items that need to be clarified, the buyer can process the work item again.

RELATED POSTS

WORK FLOW IN MM PART TEN
SAP security infrastructure for data production

Work Flow Scenarios in Material Management of SAP ABAP Part Eight

Operation/Link to Appl. Functionality (MM-PUR-GF)

The following description is based on the assumption that a purchase order is created that is subject to a release strategy.

Creation of Purchase Order

A user creates a purchase order via Logistics _ Materials management _ Purchasing _Purchase order _ Create. This PO fulfills the conditions of a release strategy. Saving results in the creation of an object of the type Purchase order.Working Through the Release Strategy The PO must be released using all the release codes defined in the release strategy.

Non-workflow-relevant release codes

If a release code is not workflow-relevant, the user responsible can effect release as follows:

Logistics _ Materials management _ Purchasing _ Purchase order __Release

Workflow-relevant release codes

If a release code is workflow-relevant, the event that triggers the workflow,ReleaseStepCreated, is generated automatically.In the event parameter container, you will find the user name of the person who created the PO (in the element _EVT_Creator), the reference to the PO (in the element _EVT_Object), and the release code (in the element ReleaseCode).The user responsible finds a work item representing the standard task Release purchase order in his or her SAP Business Workplace inbox. Processing this work item allows the PO to be released.You can access the SAP Business Workplace via Menu _ Business Workplace.

Settlement Accounting re Rebate Arrangements in Purchasing (MM-PUR-VM)

In Purchasing, rebate arrangements are stipulations agreed with vendors governing refunds of part of the buying entity’s total spend over a certain period. Such refunds often vary according to the volume of business done with (i.e. volume of purchases made from) the vendor. The volume of business done with the vendor and the resulting rebate can only be determined retrospectively, at the end of the period (subsequent to the individual transactions of which this business volume is composed). The calculation of the rebate and the subsequent transfer of the relevant data to Financial Accounting is described as settlement accounting with respect to the rebate arrangement.Settlement accounting can be carried out periodically during the overall validity period of the rebate arrangement and/or once-only, at the end of this period.

Process Flow The Purchasing staff who entered into the relevant rebate arrangements with the vendors can be advised by workflow when the planned settlement dates are reached.A work item appears in their inboxes on each settlement date. From within the work item, the responsible member of staff can directly invoke the settlement accounting transaction with the rebate arrangement affected.Prior to settlement, it may be necessary to compare and agree business volume data with the vendor. A work item is created for this process as well.

Technical Realization (MM-PUR-VM)

Object Types Used

Object technology is used to create the interface between the R/3 functionality and the Workflow system.For this reason, the information given below is primarily of a technical nature. You need this information only if you are interested in details of the implementation or wish to create your own enhancements.

Object type BUS3030 (rebate arrangement, Purchasing).

Standard Tasks

The standard tasks provided by SAP as single-step tasks describe basic business activities from an organizational point of view. A single-step task relates to a single object method (= technical link to R/3 functionality) in each case, and is linked to its organizationally possible processors.

Object Type: BUS3030 (Rebate Arrangement,Purchasing)

Definition

A rebate arrangement is an understanding with a business partner relating to the granting of rebates over a certain period.A rebate arrangement can be entered into between a sales area and a customer (rebate recipient or beneficiary) or between a purchasing organization and a vendor (rebate granter).

Use

In the scenario, a business application object of type BUS3030 is processed, i.e. either a business volume comparison or settlement accounting is carried out with respect to a rebate arrangement in Purchasing.

Standard Task MMExBusVolCo (Perform Business
Volume Comparison re Rebate Arrangement)

Structure

Standard task for performing a business comparison and agreement process with regard to a rebate arrangement in Purchasing.

Standard task: TS00900055
Identifier: MMExBusVolCo

Description: Business volume comparison for rebate arrangement
Structure Object Method Referenced
Object type: BUS3030 (rebate arrangement, Purchasing)
Method: ExecuteBusVolComp (perform business volume comparison)
Processor Assignment At run time, this standard task is addressed to one or more members of the purchasing group responsible for the rebate arrangement. A necessary prerequisite for this is the assignment of the responsible purchasing groups to the desired organizational units or positions of organization management .

Standard Task: MMRebAgSettl (Perform Settlement Accounting re Rebate Arrangement)

Definition

Standard task for performing settlement accounting with respect to a rebate arrangement in Purchasing.

Standard task: TS00900058
Identifier: MMRebAgSettl

Description: Perform settlement accounting re rebate arrangement Structure Object method referenced.

Object type: BUS3030 (rebate arrangement, Purchasing)
Method: Settle Processor assignment: At runtime, this standard task is addressed to one or more members f the purchasing group responsible for the rebate arrangement. The same settings are necessary as for the standard task TS00900055.

Workflow Template MMRebAgSettl (Settlement Accounting re Rebate Arrangements)

Definition

Work template to perform settlement accounting with regard to a rebate arrangement.If the system recognizes that final or interim settlement accounting is due with respect to a rebate arrangement in Purchasing because a settlement date has been reached, a workflow is started with template MMRebAgSettl.

Workflow template: WS00900007
Identifier: MMRebAgSettl

Description: Settlement accounting with regard to rebate arrangements (Purchasing)
Triggering Events for Workflow Template The events ToBeSettledInterim (partial settlement re rebate arrangement in Purchasing) and ToBeSettledFinal (final settlement re rebate arrangement in Purchasing) are entered as triggering events for the workflow template for object type BUS3030 (rebate arrangement, Purchasing).This “linkage” between the event and the workflow template to be triggered is deactivated in the standard system and must first be activated in Customizing for SAP Business Workflow if the workflow template is actually to be started.

Workflow Container and Data Flow

The important information that must be available during the course of the workflow is the object reference to the rebate arrangement to be processed (_Evt_Object). The information is available as an event parameter in the container of the triggering event, and must be passed on from there to the workflow container via data flow.As a result, the following data flow definition between the triggering event and the workflow container is defined in the standard system:

Workflow container Event parameter container

RebateAgreementPurch _Evt_Object

The element RebateAgreementPurch has been created in addition to the elements available in the standard system.

Steps in the Workflow

1. You can start workflows for rebate arrangements in respect of which settlement is due via a program.
2. For each selected rebate arrangement, the system checks whether a settlement date has been reached. If a date for interim or final settlement has been reached, a workflow is started.

Workflow Template MMRebAgSettl (Settlement Accounting re Rebate Arrangements)

A separate workflow is started for each rebate arrangement settlement date.

3. The attribute BusVolCompNec (business volume comparison and agreement necessary) of the object "rebate arrangement, Purchasing" indicates whether a business volume
comparison and agreement process is necessary prior to actual settlement.

If this is the case, a work item is generated to carry out this process. This appears in the inboxes of all members of the purchasing group responsible for the rebate arrangement.If this is not the case, or after this step, the system generates a work item to carry out actual settlement. The members of the responsible purchasing group receive this item in their inboxes too.

RELATED POSTS

WORK FLOW IN MM PART 9

SAP Authorization and ALE

SAP Network Level Security
Mysap web application server

Work Flow Scenarios in Material Management of SAP ABAP Part Seven

Steps in a Workflow (MM-PUR-GF)

If the release code with which the document is to be processed according to the release strategy is workflow-relevant, a workflow is started and a release work item generated. If a user whom workflow control identifies as being responsible for this release code logs on to the system, this user will see this work item in his or her SAP Business Workplace inbox.If, for example, a job is assigned to the release code as a processor ID and several users are allowed to work with this release code, all of these users will see the same work item in their in boxes.An individual workflow is started for each workflow-relevant code.

The processing of the work item results in the event Release effected. This event terminates the task Release . The entire workflow is ended when the person who created the document receives a confirmation per work item and has processed this work item.The terminating event significantly changed can also occur outside the workflow process.

Changes After the Start of the Release Procedure Changes can only be made to a document if no other user is currently processing the document and no follow-on document has yet been generated (such as an RFQ from a purchase requisition, or a PO from an RFQ).In the following, we discuss what happens when a document for which the release procedure has already commenced is changed. The following possible situations may arise:

Changes that do not necessitate a different release strategy
Significant changes necessitating a different release strategy
Since the first case does not necessitate another release strategy, it will not be discussed further here.If the change is significant, the right-hand path in the graphic would thus be taken, and the workflow terminated due to the occurrence of an event external to the workflow process. This has the following consequences:

If the document has already been released for follow-on processing, it is blocked again by the application and must be processed in accordance with the new release strategy.If a work item was generated, it is no longer visible in the processor’s SAP Business Workplace inbox.

Workflow Definition: Details (MM-PUR-GF)

The following details are of interest in connection with the workflow definition. Look at the definition in the system.

Data Flow

The following data flow is defined for each of the steps Release , Confirmation of cancellation, and Confirmation of release:
Task container Workflow container _WI_Object_ID <-
ReleaseCode <- ReleaseCode The elements and ReleaseCode have been created in the workflow container in addition to the elements available in the standard system and are supplied from the triggering event.

Determining the Processor

The processor determination facility is stored in the tasks Release and not in the workflow definition.
Result of Processing and Termination of Workflow

Once the user has processed the document using his or her release code, the document counts as “released”. This status information is placed in the SAP Business Workplace inbox of the document creator (Initiator) as a work item. When this work item has been processed, the workflow is terminated.The terminating event significantly changed can also occur outside the workflow process.

Use

Several other specific customizing steps are necessary for this workflow template in addition to the general customizing that is necessary to make sure that the workflow system functions properly.Classification Document release (approval) using SAP Business Workflow necessitates a link to the classification system, that is to say all characteristics used in the release conditions (such as plant, purchasing group, account assignment category etc.) must be made known to classification.

Defining the Organizational Structure (MM-PUR-GF)

Various users are able to release documents. These users must be identified in Customizing for SAP Business Workflow. They can also be assigned to various organizational units.Organizational units are a means of subdividing an enterprise according to various business criteria (for example, most enterprises are made up of different departments).Set up your organizational structure as follows:

Perform the customizing activity (Basis Components _ Business Management _ SAP Business Workflow) _ Edit Organizational Plan.

Performing Task-Specific Customizing (MM-PUR-GF)

Here you list all organization management objects that are generally allowed to effect releases with workflow-relevant release codes (e.g. jobs or positions) and classify the general tasks.

Procedure

1. Perform the customizing activity (Basis _ Business Management _ SAP Business
Workflow _ Perform Task-Specific Customizing).
2. Then, under Materials Management _ Purchasing, choose the activity Assign Tasks to
Agent (Processor).
3. Assign the task Release to the processors (“agents”) who effect release via workflow in your enterprise.
4. Classify the task Release Effected as a general task.

Activating Event-Receiver Linkage (MM-PUR-GF)

The event ReleaseStepCreated for the relevant object types is the triggering event for the associated workflow and is entered in the event linkage table as such in the standard system. For the workflow to actually be started, the linkage between the triggering event and the workflow as receiver of the event must be activated in Customizing for SAP Business Workflow.

Procedure

1. Perform the customizing activity (Basis _ Business Management _ SAP Business
Workflow _ Perform Task-Specific Customizing).
2. Activate event linkage for the workflow template Workflow for Release
(Materials Management _ Purchasing _ Activate Event Linkage).
(Alternatively, you can activate event-receiver linkage by processing the workflow directly.)

Application-Specific Customizing (MM-PUR-GF)

In Customizing for Purchasing, you define:
Which release codes are relevant to workflow
Who may effect release with which code. This assignment is plant-dependent. You have the option of defining either a direct or an indirect user assignment:

Direct

You enter a user name directly.

Indirect

You enter a job or a position, for example. At run time, the system then determines the processing staff member responsible.Take care to ensure that this assignment is compatible with the processor assignment in Task-Specific Customizing for SAP Business Workflow. If, you enter a user, for example, the latter must also be the holder of a position in Task-Specific Customizing. If you enter a position, precisely this position must also be defined in Task-Specific Customizing and have users assigned to it.

You can implement an enhancement (user exit M06E0005) for a release code if you wish to have a different role resolution than the one defined in the standard system. You make these settings via the Customizing activity (Purchasing _ Purchase Requisition _ Release Procedure _) Procedure with Classification.

RELATED POSTS

WORK FLOW IN MM PART 8
SAP web application and business server pages

Work Flow Scenarios in Material Management of SAP ABAP Part Six

Maintaining Processor Assignment

At run time, the relevant task is addressed to the processor(s) (processing staff member(s)) to whom the release code has been assigned via a role resolution. You must make the following settings in Customizing for this:

_ In Task-Specific Customizing for SAP Business Workflow you must list all organization management objects that are generally permitted to work with workflow-relevant release codes (e.g. jobs or positions).Prior to this, the organizational plan (defining the organizational structure) must be finalized.

By assigning a release code to a processor in Customizing for Purchasing, you specify who in concrete terms may process a document (i.e. effect releases) using this code. Take care that this assignment is compatible with the processor assignment in Task-Specific Customizing. If you enter a user, for example, the latter must also be the holder of a position in Task-Specific Customizing. If you enter a position, precisely this position must also be defined in Task-Specific Customizing and have users assigned to it.It is also necessary for the release codes to be marked as “relevant to Workflow”.

Determining the Processor

In determining the processor (the person who is to process the document), the system searches the Purchasing Customizing facility for the processor ID for a release code. This is achieved via role resolution.For this purpose, the following roles are defined for the relevant task:

Request for Quotation (RFQ)
Role 20000030 (Person responsible for releasing RFQ)
Purchase Order (PO)
Role 20000027 (Person responsible for releasing PO)
Scheduling Agreement
Role 20000028 (Person responsible for releasing scheduling agreement)
Contract
Role 20000029 (Person responsible for releasing contract)

Input for the role comprises the release code and the relevant document. These were passed on to the role container from the task container.

Tasks: Release (MM-PUR-GF)

<- _WI_OBJECT_ID ReleaseCode <- ReleaseCode Then, using this data, the Customizing settings for Purchasing containing the linkage between release code and processor ID are read. After this, the system checks whether these settings agree with those of Task-Specific Customizing. If they do not, the workflow terminates and the system administrator responsible for workflow is informed by mail accordingly. Terminating Events The standard task Release is terminated by the events Release effected, or significantly changed.

Tasks: Release Effected (MM-PUR-GF)

Via these tasks, the creator of the document is informed that release has been effected (approval has been signified). He or she receives this information via the text of the work item representing the task. The creator processes the work item and thus concludes it. There is no further functionality besides this conclusion of the work item.

Request for Quotation (RFQ)

Task: TS20000177
Identifier: mm_qr_ok
Description: Release of RFQ effected
Referenced Object Method, Attributes
Object type: BUS2010 (RFQ)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Purchase Order (PO)
Task: TS20000168
Identifier: mm_po_ok
Description: Release of PO effected
Referenced Object Method, Attributes
Object type: BUS2012 (PO)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Scheduling Agreement
Task: TS20000171
Identifier: mm_pa_ok
Description: Release of scheduling agreement effected
Referenced Object Method, Attributes
Object type: BUS2013 (Scheduling agreement)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Contract
Task: TS20000174
Identifier: mm_pc_ok

Tasks: Release Effected (MM-PUR-GF)

Description: Release of contract effected

Referenced Object Method, Attributes
Object type: BUS2014 (Contract)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Maintaining Processor Assignment
These tasks should be classified as general tasks. General tasks do not have to be assigned to a processor because anyone may execute them. The processor (= creator of the document) is determined from the context of the workflow.

Workflow: Release of Purchasing Documents (MM-PURGF)

If the system recognizes that the release code with which a user must next signify approval in accordance with the release strategy is workflow-relevant, a workflow is started. An individual workflow is started for each workflow-relevant release code. A central task of workflow control is to determine the processor (several may be involved) to whom this release code has been assigned.

Request for Quotation (RFQ)

Workflow: 20000080
Identifier: wf_qr_rel
Description: Workflow for release of RFQ
Purchase Order (PO)
Workflow: 20000075
Identifier: wf_po_rel
Description: Workflow for release of purchase order
Scheduling Agreement
Workflow: 20000078
Identifier: wf_pa_rel
Description: Workflow for release of scheduling agreement
Contract
Workflow: 20000079
Identifier: wf_pc_rel
Description: Workflow for release of contract
Triggering Event for Workflow
The event ReleaseStepCreated has been entered as the trigger for the workflow for the relevant object type.This “linkage” between the event and the workflow to be triggered is deactivated in the standard system and must first be activated in Customizing for SAP Business Workflow if the workflow is actually to be started.

Workflow Container and Data Flow The most important information that must be available within the course of the workflow comprises the object reference to the document to be processed (_EVT_Object) and the release code (ReleaseCode), as well as the name of the person who the created the document Workflow: Release of Purchasing Documents (MM-PUR-GF) (_EVT_Creator). The information is available as an event parameter in the container of the triggering event and must be passed on from there to the workflow container via data flow.

Therefore, the following data flow definition between the triggering event and the workflow container is defined in the standard system:

Workflow container Event container
Initiator <- _Evt_Creator <- _Evt_Object Release code <- ReleaseCode In the standard system, the element Initiator exists in the workflow container. The elements and ReleaseCode have been created in addition to the standard elements that exist.

RELATED POSTS

WORK FLOW IN MM PART SEVEN
SAP Authorization and ALE
Authorization and implementation of SAP

SAP security infrastructure for data production
SAP safety infrastructure

Subscribe to: Posts ( Atom )