Production plan

Use this function to customize the Production plan (FUNBENCHI) function to the needs of your organization and your processes.

Your system is provided with a standard or master Production plan entry format. You can modify the master or create new entry definitions to suit your processes, your users or just to make your system more convenient to use. Each entry definition affects the way in which information is entered, and what information is displayed and printed. 

You create each entry definition as a "Transaction". Each transaction you define is available for selection when the Production plan function is loaded, either from the menu or from an action in a linked function. The default entry screen will be displayed and a choice will not be offered if you do not define additional transactions to the standard or master Production plan entry format.

 You are advised to get a basic understanding of how your system works before changing the master entry definition.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The Production plan Entry transactions function contains a Home section and one section per feature of the functionality:

Header

The transaction header allows the user to create new transaction codes or to look for existing transactions to modify or delete. It is composed of two sections:

Transaction

This is the code identifying the setup of the Production plan transaction. A description is assigned to each setup transaction code. These are two items of information that appear in the selection window proposed at the start of the production reporting entry.

Access code

Transactions can be filtered according to the users, thanks to the introduction of this access code: if the field is assigned, only the users who have this access code in their profile will be able to access the transaction.

If several transactions are set up for a function, and the user only has access to one of them because of the access codes, the selection window is no longer proposed: the access is by direct entry.

Tab Parameters

You use this section to define functional characteristics for this entry transaction. This includes the following information:

  • Which production reporting type is requested (entry to stock on WO/entry to stock on BOM).
  • Which default quantity should be used to initialize the produced quantity in the case of an entry to stock on BOM without WO?
  • If the material consumptions associated with the production reporting should be achieved                        
  • The material consumption method: this setup is used to load the quantities of consumed material based on the planned and achieved quantity.
  • Strict manual withdrawal: this setup allows the user to impose or not manual entry of the consumption of the materials with the immediate stock withdrawal method.

Tab Display

This tab makes it possible to define all the columns that should be displayed in the Production plan, along with their display order.

Also specified here is whether the quantities produced should be preloaded or not.

Tab Stock

This tab is used to set up the fields that should be displayed, entered or hidden during the entry to stock. Only the information of the detail window can be set up.

Tab Analytical

In this function, the following fields cannot be accessed:

  • Entry
  • Line distribution
  • Header section

Specific actions

Validation

Select the Validation action to save this entry transaction definition. This triggers the corresponding screens to be generated.

You should view your results to check the display is as you expected. Should you need to make further adjustments you can adjust your definition and revalidate until the results you require are displayed.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

You do not have the access rights for this code

This message is displayed if the access code defined does not exist in the user profile. Select a different access code or (provided you have the authorization) add the requested access code to the user profile.

Tables used

SEEREFERTTO Refer to documentation Implementation