Mass Cahnge Enhancment Tr

Specification - Enhancements

Mass / Mass Change Program

1 Overview

1.1 Review Information

Team Leader

Review Date

Attendees

Description

1.2 Change Log

No. Date Object Description of Change Name01 Mass/Mass Change Create document.02 Mass/Mass Change Modify document to amend original

request and add program for messaging capability.

030405

1.3 Sign-Off / Final Approval

Name Signature Date

Project Manager

Functional Team Lead Approved

Development Team Lead

Technical Team Lead

05/03/23 9:34 AM Page 1 of 11

MSOffice User, 01/03/-1,

This is the name of the team lead who is responsible for the development


Name of the person initiating the change


Object that is going to be affected by the change(Screen, Mapping, etc)


Date on which the change was requested and noted


Brief description of the interface: purpose and process


Enter the names of the persons who reviewed this document


Enter the date on which the specification was reviewed (if applicable)

1.4 CommentsNote: This program enhancement request is made in order to create an efficient tool to manage domestic and export rotational materials, as legally mandated. Significant monetary penalties are defined for violation of these regulations.

Issue # Description Assigned To / Date

Comments Resolution

05/03/23 9:34 AM Page 2 of 11

2 Table of Content1 OVERVIEW.................................................................................................................................... 1

1.1 REVIEW INFORMATION............................................................................................................... 11.2 CHANGE LOG............................................................................................................................. 11.3 SIGN-OFF / FINAL APPROVAL.....................................................................................................11.4 COMMENTS................................................................................................................................ 2

2 TABLE OF CONTENT................................................................................................................... 3

3 FUNCTIONAL SECTION.............................................................................................................. 4

3.1 GENERAL INFORMATION............................................................................................................. 43.2 ENHANCEMENT DESCRIPTION - FUNCTIONAL DETAILS.................................................................4

3.2.1 Assumptions....................................................................................................................... 43.2.2 Future Enhancements........................................................................................................ 4

3.3 PROCESS FLOW.......................................................................................................................... 53.3.1 Business Process Owner....................................................................................................53.3.2 End User........................................................................................................................... 53.3.3 End User View of Process..................................................................................................53.3.4 Frequency.......................................................................................................................... 53.3.5 Dependencies..................................................................................................................... 53.3.6 Data Flow......................................................................................................................... 53.3.7 Maintenance...................................................................................................................... 53.3.8 Other................................................................................................................................. 5

4 TECHNICAL SECTION................................................................................................................. 6

4.1 INFRASTRUCTURE....................................................................................................................... 64.1.1 Software Requirements......................................................................................................64.1.2 Hardware Requirements....................................................................................................64.1.3 Network Requirements.......................................................................................................64.1.4 Basis/Configuration Requirements.....................................................................................6

4.2 REFERENCES.............................................................................................................................. 64.2.1 Related Company Documents.............................................................................................64.2.2 Other Functional Contacts.................................................................................................64.2.3 Other Technical Contacts..................................................................................................64.2.4 Other Infrastructure Contacts............................................................................................64.2.5 Other External Contacts....................................................................................................64.2.6 Other References (Documents and/or persons)...................................................................6

4.3 DEVELOPMENT........................................................................................................................... 74.3.1 Enhancement Type............................................................................................................. 74.3.2 New Data Dictionary Objects............................................................................................74.3.3 Enhancement & component name......................................................................................74.3.4 Input Interface definition...................................................................................................74.3.5 Program Logic................................................................................................................... 8

4.5 Efforts Estimate....................................................................................................................... 10

05/03/23 9:34 AM Page 3 of 11

3 Functional Section

3.1 General Information

Functional Area Production PlanningOriginatorRequest DateDue Date

3.2 Enhancement Description - Functional Details Note: This enhancement requires two distinct capabilities which are 1) messaging and 2) material substitutions.

The general functions of the requested programs are as follows:1) Enable all BOMs for rotational products to be changed whereby a message will be added to

respective BOM “process areas” to indicate the start and finish date of the rotational window period.2) Define which unique quarterly rotational materials (i.e. – labels and cartons) are listed in bills-of-

materials (BOM) with a BOM usage status of “Production”. This is to be achieved by searching for rotational materials of interest via the SAP “material group” field. For instance, a search for all fourth quarter cartons would be done via material group 94.

Subsequent to identifying which BOMs and materials (i.e. – labels or cartons) meet the search criteria, the SAP System will also need to define the “follow-up” material listed in the MRP-4 view of the material master for each of the materials (i.e. – labels or cartons) resulting from the search.An on-line output report is to be created from the above noted, whereupon the user can initiate BOM changes consistent with the standard SAP “mass change” transaction (CS20).

3.2.1 AssumptionsThe material group number for rotational materials will maintain their current numbering convention which relates material group numbers to specific individual quarters of the year (i.e.- 81=1 st QTR, 82=2nd

QTR, etc…).

3.2.2 Future EnhancementsA future enhancement requesting the capability for mass changes of material “effective out” dates will be needed in conjunction with the immediate enhancement request.

05/03/23 9:34 AM Page 4 of 11


e.g. additional functionality/business requirements that would require scope adjustments


Any assumptions made with regards to the enhancement, deadlines, dependencies outside SAP etc.


Detailed Description of enhancement - highlight the logical complexities


Date the specification is due


Date the specification was requested


Responsible functional team member responsible for the interface


SAP Functional area for which this interface needs to be developed (SD, MM, PP, FI, CO, etc)

3.3 Process Flow

3.3.1 Business Process Owner

3.3.2 End User

3.3.3 End User View of Process

3.3.4 FrequencyThirty working days of each quarter or 120 working days of each year. Note: The SAP Go Live date is September 3, 2002 and the requested enhancement programs will need to be run just ahead of the rotational window period which “opens” approximately on September 15, 2002.

3.3.5 DependenciesIt is planned to have the enhancement program (Mass / Mass Change) work in conjunction with the standard SAP “mass change” transaction (CS20).

3.3.6 Data Flow The data set resulting from the search needs to be displayed in an on-line report format.

3.3.7 Maintenance

3.3.8 Other

05/03/23 9:34 AM Page 5 of 11


Business process related maintenance. Critical steps to ensure accurate functioning of the enhancement


High level pictorial depiction of the data flow, like flow chart


List all the prerequisites/Follow-up processes that are necessary


When the enhancement should run, how often, manual or scheduled etc


Write, in simple words, the process from an end user point of view


End User/Person using the application


External Main Business Contact for the process

4 Technical Section

4.1 Infrastructure

4.1.1 Software Requirements

4.1.2 Hardware Requirements

4.1.3 Network Requirements

4.1.4 Basis/Configuration Requirements

4.2 References

4.2.1 Related Company Documents

4.2.2 Other Functional Contacts

4.2.3 Other Technical Contacts

4.2.4 Other Infrastructure Contacts

4.2.5 Other External Contacts

4.2.6 Other References (Documents and/or persons)

05/03/23 9:34 AM Page 6 of 11


Here you will enter the related Company document that the user department might have created for this requirement.


Enter any basis support requirements and/or any configuration required like authorization objects


Any additional hardware that will be required to support this enhancement, like external EDI subsystem hardware


Any additional software that will be required to support this enhancement, like external scheduling software.

4.3 Development

4.3.1 Enhancement Type Function Exit

Field Exit Screen Exit Menu Exit

Function Module Normal RFC

Custom Program Custom Transaction (Not Report Transaction)

4.3.2 New Data Dictionary Objects

4.3.3 Enhancement & component name Mass / Mass Change – Add MessagingMass / Mass Change – Change Materials

4.3.4 Input Interface definition

05/03/23 9:34 AM Page 7 of 11


Selection screen for Custom Program, Export/Import parameters for function modules etc


Enter the CMOD, SMOD object names. Relevant only for User Exits.


Enter the Names of any new data dictionary objects created for this requirement (tables, data elements, domains, views etc: Give all relevant details about the fields, type and length etc)


Enter if the enhancement is a user exit, custom program, custom transaction etc. Double click on the relevant box to check it.


Enter the development method that will be used for this requirement (ABAP program, BAPI, LSMW, Data Transfer Workbench, etc.)

4.3.5 Program Logic There are two processes in this transaction and the user can choose one of the processes. In order to achieve this, we need to have the option as tabs on the selection screen. The first tab relates to the process ‘Add Messaging’ and the second tab relates to the ‘Change the rotational Material on BOM’. The selection screen for both the processes will be same, except that some fields are required for one process and they are optional for the other. This needs to be handled in the selection screen data validations.

Selection Screen BOM Selection Criteria

Plant ____________ like MARC-WERKS (Required, Parameter)BOM Usage ____________ like MAST-STLAN (Optional, Select-option, no-intervals, allow for max 2 values, default to 1and

2 if left blank)BOM Status ____________ like STKO-STLST (Optional, Select-option, no-intervals, allow for max 3 values, default to 21,

22, and 23 if left blank)

Component Selection CriteriaMaterial Group ____________ like MARA-MATKL (Required, Select-option, no-intervals)Characteristic ____________ like CAWN-ATNAM (Optional, Parameter)Characteristic Value ____________ like AUSP-ATWRT (Optional, Parameter)

Input valuesChange Number ____________ like AENR-AENNR (Optional, Parameter)BOM Item Text ____________ like STPO-POTX1 (Optional, Parameter, allow for 2 lines of Item text)

BDC optionsTransaction ModeUpdate Mode

Logic If BOM messaging option is selected and the BOM item text (Input Values section) is not entered, issue an error message, until the text is

entered. Check that both the characteristic name and value are entered, if entered.

05/03/23 9:34 AM Page 8 of 11


Type the program logic/algorithm here in technical terms

Find all BOMs matching the “BOM Selection Criteria” criteria from the selection screen. Go to MAST, get all the material BOMs where WERKS = selection screen value for plant and

STLAN in selection screen values for BOM Usage. For each MAST record, get all the BOM header details from STKO where STLNR = MAST-STLNR and

STLAN in selection screen values for BOM USAGE andSTLAL = MAST-STLAL.

For each MAST record, get all the alternate BOM link details from STAS where STLTY = STKO-STLAL andSTLNR = STKO-STLNR andSTLAL = STKO-STLAL.

For each STAS record, get all the BOM items from STPO where STLTY = STAS-STLAL andSTLNR = STAS-STLNR andSTLKN = STKO-STLKN.

For each component, check if the material has one of the material groups entered in the selection screen by going to MARA where MATNR = STPO-IDNRK and MATKL in selection screen values for material group. If not, skip the component.

If the characteristic name and value are entered, then get the characteristic values of each component by using the CLAF_CLASSIFICATION_OF_OBJECTS and check if the characteristic entered in the selection screen has the value entered in the selection screen. If not, skip the component.

For each checked component get the follow-up material (MARC-NFMAT) using the plant from the selection screen. Output a header giving the summary of all the values entered in the screen. Generate a detailed output report with the following headings and the menu should have buttons for Select all, Deselect all, Next screen,

Previous screen, Last screen, Print report, Add Messaging, Switch to Rotational Materials. The report should be sorted by BOM material number ascending and Alternate BOM ascending

SelectionIndicator

CurrentMaterial

Follow-upMaterial

BOM MaterialNumber

AltBOM

BOMDescription

Checkbox

########## ########## ########## 1 AAAAAAAAAAAAAAAAAAAA

Checkbox

########## ########## ########## 2 BBBBBBBBBBBBBBBBBBBBBB

Checkbo ########## __________ ########## 1 CCCCCCCCCCCCCCCCCCCCC

05/03/23 9:34 AM Page 9 of 11

x

Once the user selects some or all the records, and presses the ‘Add Messaging’, or ‘Switch to Rotational Materials’ prepare the BDC data for the processing option chosen and call transaction CS20 (See screen prints in the attached document). If the ‘Switch Rotational Materials’ option is chosen (Should we check for the existence of BOM item texts if the BOM messaging option is chosen?), then go to next step else skip the next step.

Check if the BOM item long texts already exist for the selected component by calling the function module READ_TEXT by giving OBJECT = ‘BOM’, NAME = concatenated string of all the key fields of STPO. Check if the STPO-POTX1 and STPO-POTX2 are filled in. If READ_TEXT return some lines, then use DELETE_TEXT function module to delete the texts, and if STPO-POTX1 and STPO-POTX2 are filled in, then go to CS20 transaction and blank the two fields, save and proceed to the next step.

Prepare the BDC data for the corresponding processing option chosen by the user and call transaction CS20 (See screen prints in the attached document) with options chosen from the selection screen.

4.4 Error Handling

4.5 Efforts Estimate

Task/Effort for SAP Developer User

Development 5TestingMaintenance

05/03/23 9:34 AM Page 10 of 11


Enter error handling requirements

05/03/23 9:34 AM Page 11 of 11