Ansicht
Dokumentation

SAPLV56M - Include SAPLV56M

Vendor Master (General Section)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Functional group V56M

In this functional group, there are functional modules used in the framework of Shipment collective processing transaction VT04). Additional applications are the planning proposal in transaction VT01/ VT02 as well as freight infor- mation in the order (see functional group V54P).

At this point, an overview is provided of the functional modules in this functional group. Detailed information is supplied for each individual functional module.

Shipment collective processing

In the framework of transaction VT04, deliveries can be automatically collected for shipments and these shipments can be automatically populated with data.

Using the assignments stored in the selection profile (selection variant for report RV56LFSL), the deliveries to be processed with the functional module SD_DELIVERY_FOR_TRANSPORT (func- tional group V56L) are selected from the database.

Thereafter the collective processing profile (selection variant for report RV56TRSP) is processed in which the selected deliveries are, by means of the functional module SD_SHIPMENT_COMBINE_DELIVERIES, collected for shipments. This is done in three steps:

• First, the split criteria are processed with SD_SHIPMENT_SPLIT_CRITERIA (for example, only deliveries with the same route are placed in a shipment).

• The sequence of deliveries within the shipments is assigned with SD_SHIPMENT_SORT_CRITERIA.

• SD_SHIPMENT_CAPACITY_CRITERIA checks whether the existing shipments fulfill the assigned capacity criteria. If they are too big, they are divided up into multiple shipments. If too small, they are deleted.

SD_SHIPMENT_POPULATE_DOCUMENT populates each shipment with data corresponding to the assignments (for example, route, service agent, deadlines, etc.). These assign- ments are stored in a selection variant for report RV56TRTR.

Saving is done with SD_SHIPMENTS_SAVE (Functional group V56U).

SD_SHIPMENT_VT04_PROT_SAVE stores the collective processing log and SD_SHIPMENT_VT04_PROT_OUTPUT outputs it.

Details on the collective processing logic is contained in the docu- mentation on reportRV56TRGN.

Dynamic field modification, field catalogue

The rules able to be stored in the framework of VT04 can be relatively complex.

For example, one could assign that the shipping point is to be a split criterion in shipment formation (only deliveries with the same shipping point are to be collected into a shipment). However, shipping points 0005 and 0023 lie so close to each other that deliveries from these two shipping points can be included in one shipment ( Group formation for fields).

DYN_FIELD_CATALOG_VTRLK_INIT fixes which fields of the structure VTRLK can potentially be split (or sort) criteria. This field catalogue is laid out in such a way that the functional module DYN_FIELD_CATALOG_ADD_FIELD is called up field by field. This module appends a field onto the field catalogue.

DYN_FIELD_CATALOG_F4 brings up the field catalogue which is in global memory of the functional group at that time as F4 help. The user can select a field here. The field catalogut can be defined in global memory with DYN_FIELD_CATALOG_DEFINE. An entry can be read from the field catalogue with DYN_FIELD_CATALOG_READ.

If a user now chooses a field from the field catalogue, he/she can maintain detailed information for each of these fields (to form so- called groupings). He/she can define that shipping points 0005 and 0023 are to be treated in such a way that would be considered identical (a grouping is created, comprised of 0005 and 0023).

This is done in the functional module DYN_FIELD_MAINTAIN_GROUPING which allows grouping maintenance for (almost) any field (see documentation of the functional module) This pop-up is realized with SELECT-OPTIONS. DYN_FIELD_GROUPING_SET_PFSTAT sees to it that the correct CUA status is set for PBO.

So that F1 and F4 help run correctly for grouping maintenance, the functional modules DYN_FIELD_F1_HELP or DYN_FIELD_F4_HELP are called up at these events. These call up basis functional modules which can bring up F1 or F4 help for a given field.

Planning suggestion within VT01/VT02

Within transaction VT01/ VT02, one can call up the so-called planning suggestion. This collects the (marked) deliveries according to certain rules for shipments. These rules are exactly those used in collective processing (VT04).

For this purpose, a planning profile can be allocated to each shipment type (technically speaking, this is regarded as a variant for report RV56TRGN).

SD_SHIPMENT_PLAN_PROPOSAL_INIT initializes the planning proposal with a first-time call-up. The planning profile belonging to the shipment is read from the database.

SD_SHIPMENT_PLAN_PROPOSAL_DIA brings up a pop-up in which this data can still be manually changed.

Pressing 'Execute' calls up SD_SHIPMENT_PLAN_PROPOSAL_EXEC. Here the actual planning proposal is executed which also again uses the functional modules SD_SHIPMENT_COMBINE_DELIVERIES and SD_SHIPMENT_POPULATE_DOCUMENT.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6906 Date: 20240601 Time: 173250     sap01-206 ( 117 ms )