Kontakt

Ansicht
Dokumentation

SAPLV56S - Legs is shipment

SAPLV56S - Legs is shipment

Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

There are functional modules in this functional group for processing Shipment stges.

At this point, an overview of functional modules in this functional group is displayed. Detailed information, if desired, is available for each of the individual functional modules.

The functional modules of this functional group present only a shell around the functional group STAG. The functional group STAG is the 'technical kernel' of stages processing which prepares the funcamental routine and dialogue.

The current functional group V56S is the application specific adjust- ment of this kernel to shipment processing. For the purpose of this adjustment, functional module ST_STAGES_CONFIGURE is called up, for example, with which respective return routines can be defined.

In the framework of freight charges processing, there is another shell around the technical kernel STAG which presents shipment stages from the freight charges perspective (see functional module SD_SCD_ITEM_STAGE_MAINTAIN_ALL).

Manual processing of shipment stages

The manual processing of shipment stages is executed in the functional module SD_SHIPMENT_STAGES_MAINTAIN. This calls up - as already mentioned - the configuration module ST_STAGES_CONFIGURE.

Among other things, it is specified here that, at PBO on the overview or detail screen, the form routine STAGES_EXTERN_SET_PFSTAT(SAPLV56S) is called up to set the CUA status.

Routine STAGES_EXTERN_FIELD_MOD(SAPLV56S) controls which fields are active/inactive or not able to be changed (e.g., if the shipping points and destinations of a stage can no longer be changed if the status 'Planned' is set in the shipment header).

STAGES_EXTERN_FCODE_CHECK(SAPLV56S) checks at PAI whether the execution of a functional code is allowed (e.g., if no stages can be deleted any longer if the status 'Planned' is set in the shipment header).

STAGES_EXTERN_FCODE_PROCESS(SAPLV56S) finally executes this function code. For instande, one can activate the so- called leg determination on the shipment stages screen.

Leg determination

Leg determination is an algorithm to determine shipment legs according to simple rules. For more information, see the functional module SD_SHIPMENT_LEG_DETERMINATION.

With a preliminary shipment, the GFT legs, for example, for the ship- ping harbor are determined. For this, the system must determine in what kind of main shipment the deliveries are and where it begins (origin harbor). This task is performed by the functional module SD_SHIPMENT_FIND_MAINLEG.

Routines for the processing of shipment stages without dialogue

In many cases, it is important to create, change, etc. shipment stages without dialogue. The easiest example is leg determination, but scenarios such as EDI also need this functionality.

The functional modules available for this simply call up only func- tional modules of the functional group STAG. They exist solely due to compatibility reasons and could be directly replaced ty the functional modules of the functional group STAG.

  • SD_SHIPMENT_STAGE_APPEND appends a new stage to an existing one. SD_SHIPMENT_STAGE_INSERT inserts a new stage at a certain location.
  • SD_SHIPMENT_STAGE_CHANGE changes a shipment stage.
  • SD_SHIPMENT_STAGE_CHECK can check a stage for correctness.
  • SD_SHIPMENT_STAGE_DESCRIPTIONS reads additional data and identifiers for the shipment.

Additional functions

SD_SHIPMENT_MANUAL_LEG_CREATIO is called up in the framework of exter- nal shipment planning (Functional module IDOC_INPUT_SHIPPL). Here, an IDOC can enter from an external shipment planning system with which a shipment document can be created, changed or deleted.

The geography is described in this IDOC via a sequence of locations with activities at these locations (Example: Shipping point 0001: Delivery charge 0815). SD_SHIPMENT_MANUAL_LEG_CREATIO converts this description into shipment stages.






General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 4805 Date: 20240601 Time: 080202     sap01-206 ( 85 ms )