Kontakt

Ansicht
Dokumentation

Release Information for IS-Oil Downstream Release 1.0A - MCOE ( RELNIS-OIL_1.0A_MCOE )

Release Information for IS-Oil Downstream Release 1.0A - MCOE ( RELNIS-OIL_1.0A_MCOE )

Fill RESBD Structure from EBP Component Structure   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Release Information for IS-Oil Downstream Release 1.0A - MCOE

Description

Introduction

The main areas of new functionality concern sales order, contract, and delivery entry and processing. In general, the enhancements increase the efficiency of order processing and allow some new functions to be performed. These can be summarised as capturing or displaying more information, allowing access to documents in new ways, or performing additional checks on entered data.

The following aspects of new functionality are covered in these release notes:

Sales order screen - header level

  • initial order entry screen
  • matchcode selection via sales documents per sales area
  • screen navigation
  • ship-to party entry as an alternative to sold-to party entry
  • contact details displayed for the customer
  • purchase order number required flag
  • automatic plant determination

Sales order screen - item level

  • default of handling type for excise duty determination
  • automatic plant determination for preferred then alternative plants
  • item category redetermination

Delivery document

  • external bill of lading number/miscellaneous delivery number fields
  • matchcode selection via external bill of lading number/miscellaneous delivery number
  • final delivery indicator and updating of available quantity for call- offs

Contracts

  • unit of measure conversion
  • contract-specific pricing
  • contract number in related documents

Sales order screen - header level

Description

The new IS-Oil fast order entry screen is accessed via the initial Sales Order Entry screen (transaction VA01) and is one of several overview screens that can be used. The order type entered in the initial order entry screen determines which overview screen will be accessed. To default this to the IS-Oil fast order entry screen, follow the path in customizing:

Customizing -> Implementation Projects -> SAP Reference IMG -> Sales and Distribution -> Sales -> Sales Documents -> Sales Document Header -> Define Sales Document Types

In order for the IS-Oil fast order entry screen to appear, the Fcode for the overview screen in the document type customizing table must have the value OID1.

The IS-Oil fast order entry screen is based on the double-line overview screen but contains new fields at both header and item level. The new functionality improves the efficiency of order entry by increasing the amount of data defaulted, increasing flexibility of data entry, adding ways of accessing other sales documents and displaying more customer master data. In a high volume order-taking environment, these enhancements are important to the efficient processing of orders.

Functionality

  • Initial order entry screen (MCOE.01.1)
The order type and organization structure fields (sales organization, distribution channel, and division) are required entry fields.
  • Matchcode selection via sales documents per sales area (MCOE.21.5; new request from IP test activity)
A new matchcode selection VMVA-L is available for accessing sales documents: Sales documents per sales area. The keys to this matchcode include Sold-to party and sales area data.
  • Screen navigation (MCOE.01.35, MCOE.01.36)
From the IS-Oil order entry screen the user can navigate to other overview screens, to item screens and back again. Line items can be added, changed and deleted. It is possible to save orders directly from most of the item screens without returning to the overview screen.
  • Ship-to party entry (MCOE.01.38, MCOE.01.41)
A Ship-to party may be specified as the customer and the system automatically determines the Sold-to partner for the specified Ship-to party. The contact details for the customer as entered, whether Sold-to or Ship-to, are displayed in the header data. The transportation zone for the table of alternative plants is taken from the Ship-to party. Following partner determination only the entered partner and role are displayed on the IS-Oil entry screen while the others are stored within the sales order document, where they may be viewed in the partner details screen.
  • Contact details (MCOE.01.15)
Contact person data taken from the customer master record contact person view is displayed in the header section of the order and is saved as part of the header data. The data is not alterable in the order.
  • Purchase order number required flag (MCOE.06.1)
It is possible to specify that for a particular customer, the purchase order number is a required entry field when placing orders. The purchase order number required flag is situated in the customer master record control data screen.
  • Automatic plant determination (MCOE.01.20, MCOE.01.22, MCOE.01.24, MCOE.01.21, MCOE.01.23)
In core R/3, the system proposes the delivery plant from the order header as the default plant in order items. The default header plant is taken from the customer master record shipping view or from the material master. The delivery plant may be changed manually.
With IS-Oil, alternative supply plants and associated storage locations (one preferred and four alternatives) may be specified in the customizing alternative supply plant table. Keys to the table include the transportation zone for the Ship-to party and the material group to which the material belongs. The transaction code is O5G0. Follow the path in customizing:
Customizing -> Implementation Projects -> SAP Reference IMG -> IS-Oil Downstream -> MCOE -> Alternative Supply Plant -> Set Up Plant Alternatives for Delivery.

Sales order screen - item level

Description

New fields at item level capture and display more detailed data regarding ED status, delivery plant, item category and first delivery date. This allows for greater defaulting, better integration with other functional areas (e.g. TDP - Tariffs, Duties, Permits) and more complex checking of entered data.

Functionality

  • Handling type (MCOE.01.18)
ED handling type is captured at item level and is used to determine the duty status of the combination of customer and material. For example, a material may be fully taxed, taxed at a reduced rate, or untaxed.
  • Automatic plant determination (MCOE.01.27, MCOE.01.28, MCOE.01.29, MCOE.01.30, MCOE.01.31)
The system defaults the preferred plant to item level, which is then checked for availability. If there is no availability at this plant, each alternative supply plant is checked in turn for availability. It is possible to configure the system so that for a given item category, such as consignment items, availability checking does not take place. If not enough availability is found in any of the alternative supply plants, the preferred plant is selected and a message warns the user of the stock shortage at the preferred plant. The supply plant is amended based on the result of the availability check.
  • Item category redetermination (MCOE.01.32, MCOE.01.33, MCOE.01.34)
This functionality allows for the processing of items on a consignment basis in an order. Certain products are treated as consignment and may be ordered on sales orders along with other items that are sold and invoiced as normal. The item category may be set manually but the order taker may not know which materials are to be treated as consignment. To redetermine item category automatically, an entry must be made in the table customizing view for table OID9I.
Follow the menu path Customizing -> Implementation Projects -> SAP Reference IMG -> IS-Oil Downstream -> MCOE -> Default Item Category -> Redetermine Item Category.
Keys to the table include sales area, the material group to which the material belongs, and the customer classification. The table entry specifies the standard item category and the new value which will be determined.

Delivery document

Description

New fields in the delivery document allow the user to specify more detailed external information and to indicate that no further deliveries will take place for a call-off. This action is reflected in the contract. Accessing other delivery documents is also improved by the provision of a new selection matchcode. These enhancements therefore provide more reference data and allow greater flexibility of access during delivery processing.

Functionality

  • External bill of lading number/miscellaneous delivery number fields (MCOE.20.1; NAIBR requirement)
The delivery document contains a new external details button in the header transport-related information screen and in the item details screen. This button causes a pop-up screen to be displayed, showing delivery information (external bill of lading number and miscellaneous delivery number), origin/destination information and other miscellaneous information. The same data can be accessed from the invoice document item detail screen using the same button.
  • Matchcode selection via external bill of lading number/miscellaneous delivery number (MCOE.20.18, NAIBR requirement)
Delivery documents can be accessed via a new matchcode: Deliveries by external bill of lading/miscellaneous delivery number. The keys to this matchcode include external bill of lading number and miscellaneous delivery number.
  • Final delivery indicator and updating available quantity for call-offs (MCOE.02.2, MCOE.02.4, MCOE.02.5, MCOE.02.8, MCOE02.9, MCOE02.10)
The final delivery indicator (situated in the picking overview screen of the delivery document) allows the user to specify that a given delivery is the last delivery for that call-off, even if the full amount on the call-off has not yet been delivered. The final delivery indicator cannot be set while deliveries exist for that material for which goods issue has not yet taken place. The final delivery indicator cannot be reset.
When a final delivery is made, the system updates the available contract quantity, by adding the remaining quantity on the contract to the quantity still available (e.g., not delivered from the call-off), and totals all delivery notes in the contract UoM.

Contracts

Description

The new contracts functionality enhances contract processing by increasing integration between contract, delivery, and call-off documents. Pricing in contracts allows for more specific pricing controls to be implemented.

Functionality

  • Contract-specific pricing (MCOE.04.2)
It is possible to define a contract-specific price in the call-off order and the invoice. Condition types relevant to contracts can be defined for a key combination that includes the contract number.
  • Contract number in related documents (MCOE.04.1)
The contract number is copied into related documents (call-off order, delivery, and invoice) in read-only mode. The contract number and contract item number are available in the catalogue of fields which may be used in pricing condition table creation.





CL_GUI_FRONTEND_SERVICES - Frontend Services   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 12919 Date: 20240602 Time: 015656     sap01-206 ( 236 ms )