Output Determination: Assigning the Storage Location

to a Form 
Scope of Functions
As of Release 4.6A, when printing out goods receipt/issue slips, you can also print out the address of the
storage location by enhancing the form.

You can print out the storage location address for the following output types:

 WE01 (GR slip, vers.1)

 WE02 (GR slip, vers.2)

 WE03 (GR slip, vers.3)

 WEK1 (Kanban card 1)

 WF01 (GR prod. order vers.1)

 WF02 (GR prod. order vers.2)

 WA01 (GI slip vers.1)

 WA02 (GI slip vers.2)

 WA03 (GI slip vers.3)

To print out the storage location address, you have to configure the following:

In Customizing for the enterprise structure, enter at least one address under Definition -> Materials
Management -> Maintain Storage Location . The address you want to print must have the sequence
number 001.

In Customizing for Inventory Management, set the following:

In the step Define Forms , assign the data you want to print out to the the form, for example
WESCHEINVERS1, in the sub-object window in the text elements in the "storage information".

In the output types WE03 and WA03, you have to add $*LADR-<field name>$ to the form. In all other
output types, you have to add $LADR-<field name>$.

In WESCHEINVERS1 $LADR-name1$ is given as an example. You use this to print out the name of the
storage location.

Note that:
the $ symols have to be replaced in the SAPscript editor by the & symbol.
You can choose all fields that are contained in the struture SADR (Address management: company data).
If you want to print the zip code, enter $LADR-pstlz$.

In the output types WE03 and WA03, you have to replace the form routine ENTRY_WE03 with
ENTRY_WE03L and the form routine ENTRY_WA03 with ENTRY_WA03L so that the storage location
can be changed. This means that each time the storage location is changed, a new goods receipt/issue
slip is printed.

You configure this in the step

Assign Forms and Programs.

The WESCHEINVERS3 form contains an example of what you have to change when using the form
routine ENTRY_WE03L in order to print out the storage location address after the storage location
address has changed.

For this purpose, the header of the sub-object window contains:

IF NOT $LGORTSPLIT$ IS INITIAL
Storage location $*MSEG-LGORT$ $*LADR-NAME1$
ENDIF

Transmitting Conditions and Texts from Purchase

Orders per IDoc 
Scope of Functions
As of Release 4.6A, you can transmit PO conditions to your vendors per IDoc. You can also exclude PO
texts from the transmission process in order to reduce the amount of data transmitted if the text is
particularly voluminous.

Via the IDoc view, which you can define yourself, you determine whether or not:

 The header and item conditions of the PO are to be transmitted to your vendor per IDoc.

 The header and item texts are to be excluded from transmission.

As of Release 4.6A, conditions and/or texts are transmitted only if you have created an IDoc view and
have assigned this view to your vendor in the partner profiles.

You can create IDoc views for all outbound IDoc types (ORDERS01 to 05) and the message categories
ORDERS and ORDCHG:

Tools -> Business Communication -> IDoc -> IDoc Basis -> Development -> IDoc Views.
See also
For more information, refer to the R/3 library under BC - The IDoc Interface.

MRP Areas: Mass Data Maintenance Possible 

Scope of Functions
For MRP withMRP areas, it may be necessary to assign a large number of MRP areas to a material. An
example is when materials for many automobiles are stocked in a spare parts warehouse for customer
service technicians, and each automobile is planned as its own MRP area.

Up to now, there was no specific function for maintaining this mass data. The manual assignment of MRP
areas involved a lot of effort. You had to create an MRP area segment, with specific planning and
forecasting data, for each MRP area in the materials master of the respective material.

SAP now provides six function modules (function group MD_MGD1), with which you can program your
own mass transactions.

These function modules include:

 Copy with plant template or MRP area template (MD_MRP_LEVEL_CREATE_AS_COPY)

You create new MRP area segments as a copy of the plant MRP data or as a copy of an existing
MRP area segment.

 Creation withMRP-/forecast profile (MD_MRP_LEVEL_CREATE_PROFILE)

You create MRP area segments by assigning an MRP or forecast profile, which means a record of
standard information that has been defined and saved as a profile.

 Create with data (MD_MRP_LEVEL_CREATE_DATA)

You create new MRP area segments by entering concrete MRP or forecast data.

 Change withMRP-/forecast profile (MD_MRP_LEVEL_CHANGE_PROFILE)

You change existing MRP area segments by assigning an MRP or a forecast profile.

 Change with data (MD_MRP_LEVEL_CHANGE_DATA)

You change existing MRP area segments by entering concrete MRP or forecast data.

 Set deletion flag (MD_MRP_LEVEL_CHANGE_DELETION)

You set or delete the deletion flag for MRP area segments.
SAP provides the example report RMMDDIBE which integrates all the function modules. You activate the
report by following the menu path System --> Services --> Reporting . You can save the result of the
report, and check it by accessing transaction SLG1.

The report is only an example, and is neither maintained nor developed further by SAP.

Company Code at Plant Level 

Scope of Functions
In Purchasing, purchasing organizations are not always assigned to a company code.

However, for settlement of vendor rebate arrangements at plant level in Subsequent Settlement
(settlement types 0 and 2), a company code is sometimes needed.

Sometimes, in Subsequent Settlement, currencies for business volume data or incomes may have to be
converted and the system has no reference to one of the company codes involved. In earlier releases,
any one of the company codes involved was used by the system. However, as of Release 4.6, it is
necessary to explicitly define in Customizing which company code is to be used.

This company code may also be used in message output (country, language).

Effects on Customizing
For subsequent settlement, you must assign purchasing organizations a company code in Customizing
for Purchasing. If you do not make this assignment, you may not be able to perform some functions after
the system upgrade.

Message Output for Settlement Documents and

Arrangements 
Scope of Functions
In Subsequent Settlement, you can now use message determination to create your own messages with
SAPscript for settlement runs and arrangements. You can print out the messages and send them to your
business partners for information. This function is particularly important if you perform settlement across
company codes at plant level, which means that several settlement documents are created for one
vendor. Message output from the individual settlement documents does not make sense in this case. You
can use message determination to group together this information in one form for the vendor.

Message output is controlled via the arrangement type. You can define the format of these messages
individually via the message type (Customizing).

Message determination makes use of the condition technique. In the condition technique, the following
message applications are defined for Subsequent Settlement:
  Message application "WS" (Subsequent Settlement - Arrangements) means that an arrangement
can be output via SAPscript.

You can print out information on an arrangement via SAPscript and send this to the vendor as a
confirmation, or use it internally for information purposes, for example.

 Message application "WN" (Subsequent Settlement - Settlement Run) means that output via
SAPscript for a settlement run is possible for an arrangement.

You can use this message application if you carry out settlement at plant level to group all the
information together in a single form and make this available to the vendor for information purposes.
Earlier, the only option was to create a separate printout for each plant. Now, you can group
together several plants in one printout. The business volumes and incomes from Subsequent
Settlement are added up for all the individual plants.

Effects on Existing Data

If settlement accounting has already been performed for an arrangement, it is not possible to produce this
information subsequently.

Effects on Customizing
In Customizing for Subsequent Settlement, you can define separate message schemas and message
types for message determination for each application. In Customizing, you then assign a schema and a
message type to an arrangement type.

New Configurable Messages in Customizing 

Scope of Functions
For Release 4.6A, you can configure the following new messages in Customizing for Inventory
Management in the step Define Attributes of System Messages :

 M7 327

When you enter a goods receipt with reference to an inbound delivery with the transaction MB0A
(goods receipt for unknown purchase order) and, in the process, enter a delivery note number that
does not match the identifier in the inbound delivery, the system issues a warning message.

 M7 328/329

When you receive goods for a purchase order with an inbound delivery, the system issues a warning
message in the case of an underdelivery (328) and an overdelivery (329), but only if
the WEZUO indicator is set in confirmation control in Customizing for Purchasing.

 M7 518

When you create a reservation, the system now issues a warning message when you reserve a
material handled in batches without specifying a batch.
Enhancements in Reporting for Inventory
Management 
Scope of Functions
For Release 4.6A, the functions of the following reports in Inventory Management were enhanced:

 List of material documents (RM07DOCS)

This report supersedes the old report RM07MMAT. The transaction code is MB51 as before. The
report also replaces the old report material documents for posting date (RM07MBUD, transaction
code MB59), which is now

 GR/IR list of balances (RM07MSAL)

 Display of stock in transit (RM07MTRB)

 Display customer consignment and returnable packaging stock (RM07MKON)

 Material documents with reason for movement (RM07MGRU)

The following report is new:

 Stocks with subcontractor (RM07MLBB)

This report provides an overview of the for everysubcontractor. For this report, choose Environment
-> Stock -> SC stock.

There is now information for all the reports above about authorization checks that have failed. If you do
not have authorization to display documents, in a list the system shows you where data cannot be
displayed because you do not have authorization.

You can switch the list to a non-hierarchical format. In this non-hierarchical list, you can form subtotals
over the number of columns you wish (even several levels) and form totals correctly over various units.

Setting print functions

If you want to print the output list of a report, you can print the following information at the same time:

 Entries on the selection screen

 List status

 Separate title page

These print functions can be configured for the following reports:

 Manage held data (MMIM_PREDOC_MAINTAIN)

 List of material documents (RM07DOCS)

  List of stock values: Balance display (RM07MBST)

 Material documents with reason for movement (RM07MGRU)

 Displaying consignment stock and returnable packaging stocks (RM07MKON)

 Stocks at subcontractor (RM07MLBB)

 GR/IR list of balances (RM07MSAL)

 Displaying stock in transit (RM07MTRB)

You can define these print functions in Customizing for Inventory Management in the step Set Up Print
Functions for Reporting . You can also configure for these reports whether the non-hierarchical list with
enhanced usability and functions should be displayed.

Define field selection for list of material documents (RM07DOCS)

In the report for displaying material documents, in Customizing for Inventory Management, you can
configure both the selection screen and the number of fields contained in the field catalog. You can
improve performance, for example, by decreasing the number of fields in the field catalog. See the
step Define Field Selection for List of Material Documents.

Conversions to the ABAP List Viewer

The following reports were converted to the ABAP List Viewer:

 Plant availability (RM07MWRKK)

This report supersedes the old report RM07MWRK. The transaction code is MB53 as before.

 Display physical inventory overview (RM07IDOC)

 Display physical inventory documents for material (RM07IMAT)

 Display physical inventory data for material (RM07IINV)

For more information, refer to the relevant report documentation.

New Customer Exit for Entering the Storage

Location 
Scope of Functions
As of Release 4.6A, there is a new customer exit Filling the storage location field ( MBCF0009).

Using this customer exit, the system can determine a storage location when you enter a goods
movement, depending on the data you enter.
For a detailed description of the customer exit, refer to the relevant documentation.

You can maintain customer exits in the R/3 System by choosing Tools -> ABAP Workbench -> Utilities
-> Enhancements -> Project management (transaction code CMOD).

Enhancements for Storing Documents with SAP

ArchiveLink 
Scope of Functions
As of Release 4.6A, you can use SAP ArchiveLink to store inventory count results that have been entered
on paper and assign them to the relevant R/3 physical inventory documents. For more information, refer
to the SAP library under BC - Basis -> Basis Services -> SAP ArchiveLink - Application Scenarios ->
Storage Scenarios MM.

Terminology change Prior to Release 4.6A, the step in Customizing of goods receipt for storage of
incoming documents was called Activate Optical Archiving.

Due to a terminology change, this step has been re-named for Release 4.6A as Activate Storage of
Incoming Documents .

BAPIs in Logistics Invoice Verification 

Scope of Functions
For Release 4.6A, the following new methods are available in Logistics Invoice Verification (BAPIs). The
name of the function module is shown in brackets.

 Business object IncomingInvoice

 CancelSingle (BAPI_INCOMINGINVOICE_CANCEL)

Cancel/reverse invoice

 CreateFromData (BAPI_INCOMINGINVOICE_CREATE)

Create invoice

 GetDetail (BAPI_INCOMINGINVOICE_GETDETAIL)

Display invoice

 GetList (BAPI_INCOMINGINVOICE_GETLIST)

List invoices
  ReleaseSingle (BAPI_INCOMINGINVOICE_RELEASE)

Release invoice

To display the methods, choose Tools -> Business Framework -> BAPI Browser.

For more information, see the accompanying BAPI documentation.

Logistics Invoice Verification: Aggregation 

Scope of Functions
As of Release 4.6A, you can aggregate invoice items on the Invoice Overview (MR1B), that is, you can
group together several items in an invoice according to certain criteria. The criteria are: delivery note,
purchase order, plant and material. The aggregation only refers to the display of the invoice items.

Use aggregation for invoices containing large numbers of invoice items or if the invoicing party sends you
invoices containing totals lines, such as by delivery note. Aggregation can considerably reduce the search
for possible variances.

Logistics Invoice Verification: Message Display 

Scope of Functions
As of Release 4.6A, you can display messages in the following transactions:

 Change Invoice Document (MR2M)

 Display Invoice Document (MR3M)

 Logistics Invoice Verification (MIRO)

 Logistics Invoice Verification (MR1M)

is no longer supported as of Release 4.6A.

You can display messages at header level and item level, for example, a letter of complaint, that the
system sends to the vendor on the basis of an invoice reduction.

You can use Determination analysis to analyze the reason for messages that were created in error.

Logistics Invoice Verification: Workflow for Price

Block 
Scope of Functions
As of Release 4.6A, you can use the workflow Release Invoices Blocked for Price Reasons.

If an invoice contains at least one item that is blocked because of a price variance, the system triggers the
workflow event IncomingInvoice.blockedPrice. The buyer determined receives a work item and can
display and process the list of invoices blocked for price reasons.

Analyzing invoices blocked for price reasons

The buyer can display the following environment information for an invoice item blocked for price reasons:

 Invoice

 Purchase order

 Notes

Processing invoices blocked for price reasons

The buyer can choose between three types of processing:

 Changing purchase orders

For selected blocked invoice items, the buyer can change the relevant purchase orders. If all
purchase orders are changed, the system checks if the price blocks on the invoice items become
invalid due to the changes made to the order prices. If this is the case, the system deletes the
blocks. If there are price blocks that still need to be resolved, the buyer can choose another type of
processing.

 Releasing invoice items

You can delete the blocking reasons for the selected blocked invoice items. The system checks if
the buyer has authorization to delete the blocking reason for the selected items. If this is the case,
the invoice items blocked due to price are released. If there are price blocks that still need to be
resolved, the buyer can choose another type of processing.

 Flagging invoice items as unresolvable

The buyer uses the generated object services memo function on the invoice display to document
selected blocked invoice items that are flagged as unresolvable . The system saves the price
blocks that are flagged as unresolvable. If there are still items that need to be resolved, the buyer
can choose another type of processing.

Ending the workflow

When the buyer has processed all invoice items, the workflow ends as far as he or she is concerned.

If price blocks are flagged as unresolvable, the system creates a work item for the accounts payable
clerk. He or she can display the invoice items blocked for price reasons and read the buyer's notes.

The accounts payable clerk now explicitly ends the workflow.

Consequences for system administrator

You need to assign authorization to users who are to release invoices blocked for price reasons. The
system checks the following authorization objects when releasing invoice items blocked for price reasons:

 M_BEST_BSA, M_BEST_EKG, M_BEST_EKO, M_BEST_WRK

Authorization to display purchase orders (activity 03) and order changes (activity 02)

 M_RECH_WRK

Authorization to display invoices (activity 03)

 M_RECH_EKG

Authorization to delete (change invoices) the blocking reason Price (activity 02)

See also
For more information, see the section on Workflow in the R/3 Library.

New Parameter ID MB_SORT for Storage Location

Selection and Batch Selection 
Scope of Functions
As of Release 4.6A, the parameter identifier MB_SORT exists as a sort specification for the storage
location and batch selection list.

To sort the list in a particular order, you can enter the following values for the parameter:

 ABST: Qty in descending order

 AUFS: Qty in ascending order

 FIFO: First in first out

 LIFO: Last in first out

 FIFV: Shelf life exp. date in ascending order

 LIFV: Shelf life exp. date in descending order

To set these parameters for a user, choose System -> User defaults -> Own data. In
the Parameter tab, you can enter the parameter and the desired value.

For more information on storage location selection and batch selection, refer to the MM Inventory
Management component of the R/3 library.
New Customer Exit when Posting Reservations 
Scope of Functions
As of Release 4.6A, there is a new customer exit Updating a Reservation ( MBCF0007).

Using this customer exit, you can prepare for further processing the header and item data for reservations
that were posted with the transactions MB21 (create reservation) and MB22 (change reservation).

For a detailed description of the customer exit, refer to the relevant documentation.

You can maintain customer exits in the R/3 System by choosing Tools -> ABAP Workbench -> Utilities
-> Enhancements -> Project management (transaction code CMOD).