Ansicht
Dokumentation

FSH_SEASON_RED - Mass Season Processing

ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Purpose

You can use this report to carry out mass season processing. Mass season processing refers to the following activities that can be carried out for multiple purchase orders, sales orders, stock transport orders, and purchase contracts:

• Re-determine seasons

• Manually assign seasons

Even though these activities can be carried out for multiple documents at a time, you can carry out only one activity at a time. That is, you can either re-determine seasons or manually assign seasons. You cannot carry out both activities at the same time.

Note:

You can only run this report for documents that you have already created, irrespective of whether the season has already been determined for that document.

Integration

Prerequisites

Mass season processing is based on the season data that you entered in the article master along with the Customizing for season maintenance for your document type.

• For sales documents, you enter the data in the Customizing activity Maintain Sales Documents per Sales Area for Fashion Management under SAP Customizing Implementation Guide → Sales and Distribution → Sales → Sales Documents -> Sales Document Header.

• For purchasing documents such as purchase orders and stock transport orders, you enter the data in the Customizing activities under Maintain Purchase Order Types per Purchase Area for Fashion Management for Fashion Management and Maintain Stock Transport Order Types per Purchase Area for Fashion Mgmt under SAP Customizing Implementation Guide → Materials Management → Purchasing → Purchase Order.

• For purchase contracts, you enter the data in the Customizing activity Maintain Document Types for each Purchasing Area in Fashion under SAP Customizing Implementation Guide → Materials Management → Purchasing → Contract.

You must have assigned the change activity as one of the Permitted Activities in the following authorization objects to re-determine the season for the sales and purchasing documents.

Authorization Objects	Description
V_VBAK_VKO	Sales Document: Authorization for Sales Areas
V_VBAK_AAT	Sales Document: Authorization for Sales Document Types
M_BEST_BSA	Document Type in Purchase Order
M_BEST_EKO	Purchasing Organization in Purchase Order
M_BEST_EKG	Purchasing Group in Purchase Order
M_RAHM_BSA	Document Type in Outline Agreement
M_RAHM_EKG	Purchasing Group in Outline Agreement
M_RAHM_EKO	Purchasing Organization in Outline Agreement

Features

You use this report for the mass season processing of all documents that you have already created. You can execute the mass season processing in one of the following cases:

• If you change Customizing for season processing for the sales or purchasing document type per sales or purchase area.

• If you add a new season and define periods for the season in the article master.

• If you enter or change the sales or purchase periods in the season master data.

The report performs the following tasks:

1. Checks whether the document like sales documents, purchase orders, or stock transport orders has follow-on documents

• If follow-on documents exist, mass season processing is not carried out

• If no follow-on documents exist, mass season processing is done at item level

Note:

This check is not relevant for purchase contracts.

1. Checks whether the document is locked

• If the document is locked, mass season processing is not carried out

• If the document is not locked, mass season processing is done at item level

1. Checks whether the document is a main multi ship-to order document and the child orders have already been created using the MSO Explosion report (transaction FSH_MSO)

• If the child sales orders are already created, mass season processing is not carried out

Selection

To run the report on all the documents that you have created, select the Sales Documents or Purchase Documents document type.

Note:

• If you choose Sales Documents, you have to enter the Sales Document or the SD document categ.

• If you select Purchase Documents, the Purchase Order/Stock Transport Order radio button is automatically selected.

You can select Purchase Contracts if you need to perform mass season processing for purchase contracts. You have to enter the Purchasing Document or the Purchasing Doc. Type information.

If you enter the sales document number or the purchase document number, you do not have to enter the SD document category or purchasing document type.

To view whether the follow-on documents exist for the selected document type, select Incl. Doc. with Follow-on Doc. You can view the follow-on documents for the selected document type in the log. Mass season processing will not take place for documents of this type. If you do not have the change activity as one of the Permitted Activities in the relevant authorization objects for the selected documents, these types of documents are not included in season redetermination. You can view the list of documents for which you do not have the necessary authorization in the application log. You can also use the transaction SLG1 to view the application log.

Note: The option Incl. Doc. with Follow-on Doc. is not applicable for purchase contracts as all types of purchase contracts(with or without follow-on documents) are applicable for mass season processing.

If manual season assignment has to be done, select Manual Assignment. Main items and sub items (generic article and variants) are then displayed. Now, manual season assignment can be done at generic article level, at variant level, or at single article level. This assignment can only be done for seasons maintained for that article in the article master. This assignment cannot be carried out as a background job.

If you do not select Manual Assignment, only the main items are displayed.

Note: You can also carry out mass season processing of all document types associated with a material by entering the material number or season details such as season year, season, and so on.

The mass season processing status message Season checked for generic articles; check log for variant results that is issued for a generic article does not convey the status for all the variants of the generic article in that document item. To see the complete status, check the log.

To limit the number of documents for which mass season processing has to be carried out, you can provide more details of the document based on the selected document type. For example, if you select Purchase Documents, enter the purchase organization, vendor, or the purchase group and if you select Sales Documents, enter the sales document type, sales organization, distribution channel, or the division.

1. Choose Execute.

The document number, item, article, season year, season collection, and theme are displayed on the next screen.

1. Select the documents for which you want to carry out mass season processing.
2. You can now choose either one of these options:

• Choose Simulate to simulate mass season processing. In this case, actual mass season processing is not carried out in the documents, but the mass season processing process is only simulated and processed seasons are displayed. You can use the result to decide which seasons to process. In this case, the system database is not updated with the new season information.

• Choose Execute to carry out mass season processing. The system performs the mass season processing and the new season information is updated in the document or documents.

• Choose Manually Assign Seasons to assign seasons to one or more documents manually.

• Choose Mass Adoption to assign seasons to multiple documents. This helps you save the time and effort involved in individually assigning the same season to a large number of documents.

Note: You cannot use this report for the mass processing of value-added services (VAS) items as VAS items are not season relevant.

Parallel Processing

To simulate the parallel processing of the report, choose Simulate. In this case, actual mass processing of seasons is not carried out in the documents, it is only simulated in the background and the processed seasons are displayed. The system database is not updated with the new season information.

To run the report in the background, choose Execute. The system performs the mass season processing and the new season information is updated in the documents. If you also choose Simulate, mass season processing is also carried in the background.

Note:

Any preceding and subsequent documents related to the selected documents are not included in mass season processing.

Mass season processing is either performed for a component or for the header of a structured article even when both the component and the header are season-relevant.

Example:

If a structured article has ERLA as the Item Category Group and is season-relevant, then its components are not season-relevant. In this case, mass season processing can only be carried out for the structured article and not for its components.

In the case of a structured article that has LUMF as the Item Category Group, the opposite is true. That is, the structure is not season-relevant, but its components are season-relevant. In this case, mass season processing can be carried out for the components of the structured article but not for the structured article itself.

Note: Articles with LUMF as the Item Category Group are relevant for sales documents but not in purchase documents.

Parallel processing can be carried out with the following information:

• Logon/Server Group

• Packet Size

• Max. No. of Parallel Processes

• Maximum Wait Time

If you do not maintain any values for the above mentioned parameters, the system uses the following default values:

• Packet Size = 1000

• Max. No. of Parallel Processes = 5

• Maximum Wait Time = 30 seconds

You cannot use this report to redetermine seasons for allocated items.

To carry out mass season processing for allocated items, you first have to deallocate them by either making changes to the season in VA02 or ME22N or by deallocating the sales order, purchase order, or

stock transport order in the Order Allocation Run (ARun) Optimizer.

Note:

To reallocate the sales order, purchase order, or stock transport order after the mass season processing, you can use ARun (Online), Batch ARun, or the ARun Optimizer.

The system uses the Change BAPI for updating seasons. During this update, if there is an error in even one line item of the document, the entire document is not updated.

Standard Variants

Output

Activities

To access this report, on the SAP Easy Access Retailing (W10M), choose Cross-Application Functions > Seasons > Seasons Mass Season Processing.

Example

BAL_S_LOG - Application Log: Log header data   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 15308 Date: 20240531 Time: 114556     sap01-206 ( 221 ms )