Functionality
Requests a set of demands to be planned into a capacity and materialfeasible and production plan within an external planning system.
The function module takes the Sales and Production Figures, the TargetStock Levels and the Target Day's Supplies for materials and productgroups from SOP, takes into account the Opening Stock Levels andMaterial Availabilities and executes planning steps defined in theplanning strategy under consideration of certain parameters. The resultof the planning is a set of production figures, a ProblemIdentification list and Plan Attributes that relate to the currentplanning run.
The steps executed within the external planning system is expected tobe the following:
manage the copying of a saved plan to a separate work space.
return the corresponding port number(s)/planning handle information.
insert / change orders in the system according to the new sales and
production figures.
dependent on the selected planning strategy setup the target stock
level and the target day's supply.
Convert the material availability numbers into material constraints.
Update the opening stock levels in the system according to the new
figures.
Perform necessary locking of materials and / or time periods.
Execute planning steps defined in the planning activity.
Extract and return new production figures from plan.
Extract and return problem list / planning attributes list / planning
protocol.

Notes
If in the flag I_SOPCTR-SPLFLG is set, it is only allowed to manipulatethe materials through planning, that are contained in the tableIO_SOPTAB. If the flag I_SOPCTR-SPLFLG is not set, it is allowed tomanipulate every material through planning.
The planning actions defined in the table I_PLACT shall be executedlike one planning step.
In the table I_MBEST are only materials or product groups contained,that are also contained in the table IO_SOPTAB. If for one of thesematerials no record is contained in the table I_MBEST, the openingstock level shall be zero.
The table I_MALLOC contains typically materials, which are lowest levelmaterials in the BOM or Rough-Cut Planning Profile. If a lowest levelmaterial is not contained in the table I_MALLOC it shall be defined asinfinitly available.
If the flag I_SOPCTR-REQONLYFLG the table I_PLACT, the table I_MBEST,the table I_MALLOC and the table I_PARDEF is empty. In this callingmode it is only required to return the current production figures forthe periods, that are specified in the TABLE IO_SOPTAB, which containsa record for each requested period. In addition to this the TABLEO_PROLIS and the tables O_PLATT AND O_PLPROT are required to be filled.
The fields I_SOPCTR-BEGIN und I_SOPCTR-PENDE define the date range forwhich the planning shall take place, i.e. for which the productionfigures shall be returned.

Description
The structure receives

• the port number of the stored production plan in the field PLHNDL_PUB
and

• the port number of the production plan in the field PLHNDL

from the external planning system.

Description
The structure sends


• the model name in the field MODEL,


• the planning version in the field VERSION,


• the plan Initialization flag in the field PLINIFLG,


• the single planning flag in the field SPLFLG,


• Port number in the field PLHNDL,


• the language key in the field LANGU,


• the planning target flag in the field PLTARFLG,


• the planning start in the field BEGIN,


• the planning end in the field PENDE and


• the request only flag in the field REQONLYFLG

to the external planning system.

Description
The table sends SOP planning table information to the external planningsystem and returns updated production figures from the externalplanning system.
It sends


• a list of materials and product groups for certain plants in the
columns
PMNUX and
WENUX,

• for each material/plant combination or product group/plant combination
a number of periods in the columns
PERID
PERKZ
PERIV
ERTAG
LETAG
ATAGE

• and the figures from the planning table for each of these periods in
the columns
ABSAT
PRODU
LAGRZ and
REICZ.
The periods sent to the external planning system can be mixed, i.e.start with daily periods, continue through weekly until monthlyperiods. Also the periods can be defined differently for everymaterial/plant combination or product group/plant combination.
The external planning system is supposed to send back the field PRODUfor each of the records that were sent to the external planning systemin this table. This means, the external planning system has to sendback exactly the same periods as it was requested.

Description
Contains .
The table sends availability quantities for material and product groupsto the external planning system.
It sends


• a list of materials and product groups for certain plants in the
columns
PMNUX and
WENUX,

• for each material/plant combination or product group/plant combination
a number of periods in the columns
PERID
PERKZ
PERIV
ERTAG
LETAG
ATAGE

• and the availability quantities for each of these periods in the field
MALLOC
The periods sent to the external planning system can be mixed, i.e. bedaily periods, weekly, monthly or freely defined posting periods. Alsothe periods can be defined differently for every material/plantcombination or product group/plant combination.
Each material/plant or product group/plant combination that hasinfinite availability is not contained in this table.

Description
The table sends initial stock quantities for materials and productgroups to the external planning system.
It sends


• a list of materials and product groups for certain plants in the
columns
PMNUX and
WENUX,

• and the initial stock quantity for each of these materials and product
groups in the field MBEST.
Contains only records for end item materials and product groups not formaterials on lower levels of the BOMs or rough-cut planning profiles.
If the opening Stock Level is zero, there is no record for the materialor product group in the Table.

Description
Sent to the external planning system.
Contains the parameters described by


• parameter number,


• parameter name and


• parameter value

that are necessary for the execution of planning action steps.
They are interpreted by the external planning system.

Description
Sent to the external planning system.
Contains the planning actions, that shall be executed within a planningrun in the external planning system.
The steps are numbered and the step's coding is a character string,that has to be interpreted by the external planning system.

Description
This Table is currently not used, but needs to be received anyway.

Description
If the external planning system has to report some planning attributesback to the R/3 system, it can do it by populating this table.
This table can be filled with different reports, each of which consistsof different planning attributes. In this case


• The column PLREPNAME contains the name of the respective report,


• the column PLATTNAME contains the name of the planning attribute,


• the column PLATTDES contains a short text description of the planning
attribute,

• the column PLATTVAL contains the value of the planning attribute and


• the column OUTLEN contains the output lenght of the planning attribute.

Also, it is required to describe a problem in the planning problem listby a certian number of attributes. In this case

• the column PROBCAT contains the problem category of the corresponding
planning problem,

• the column PLRLNCNT contains the planning problem number,


• the column PLATTNAME contains the name of the planning attribute,


• the column PLATTDES contains a short text description of the planning
attribute,

• the column PLATTVAL contains the value of the planning attribute and


• the column OUTLEN contains the output lenght of the planning attribute.

Description
Received from the external planning system.
The external planning system's planning log is divided into separatelines, numbered and written as single records in this table by theexternal planning system.


• The line number is written into the column LINCNT,


• the line content is written into the column LINCONT.

Description
This table is sent back by the external planning system and containsplanning problems that remain unresolved by the planning processgrouped by category.
For each single planning problem a record is contained in this table.


• The problem category is contained in the column PROBCAT.


• Each problem has an individual problem number contained in the column
PLRNCNT.

• If the problem refers to a certain R/3 object, the key of the object
may be contained in one of the following columns:
ARBPL,
WERKS,
MATNR,
DATU,
PERID,
PERKZ,
PERIV.