Tm Process and Architecture Training Session

parminder led a training session on Tm process and architecture, focusing on issues with finance configurations and the creation of service entry sheets. He emphasized the importance of completing coding assignments on time, as it is a crucial step in the initial setup process, and encouraged everyone to start the Fury course, aiming to watch at least three 10-15 minute videos per week. Clarifications were made regarding the system's behavior when creating freight orders, the impact of sales order rejections on freight units, and the potential for a Freight Settlement Document to be posted before the PGA is completed. parminder also indicated that the Freight Unit Building Rules (FUBR) would be discussed in a future session.

Master Data, End User Scenarios, and AI

parminder underscored the importance of understanding end user scenarios and master data in using their system effectively, advocating for a step-by-step approach starting with simple scenarios. He detailed the necessary components of the enterprise structure and configurations required for the system to function smoothly, and cautioned against unauthorized changes that could lead to system breakdowns. Lastly, he hinted at a separate session discussing the impact of AI on the consultant role.

SAP Configuration and Company Codes Creation

parminder led a comprehensive discussion on configuring SAP, specifically focusing on the creation of company codes. He emphasized the importance of understanding the system's functionality without delving into its inner workings, and provided practical tips for creating company codes and handling potential issues. parminder also clarified system-related instructions, the use of the transport request feature, and the process of configuration transfers between systems. He encouraged team members to learn from each other and assured them of a document detailing the tables used for freight orders and units. He also highlighted that while the initial setup is manual, 80-90% of the process will be automated with SAP, with the remaining 20% requiring manual intervention.

Plant and Company Codes Assignment Process

Parminder discussed the process of creating and assigning new plant and company codes, highlighting the necessity for careful and accurate assignment to avoid data discrepancies. He also addressed a specific error related to the valuation grouping code and committed to resolving it. Furthermore, he explained the financial configuration for a sales system, stressing the importance of correctly assigning valuation areas and activating the material ledger for logistics transactions. Finally, in response to Vadiraj's question, Parminder confirmed the necessity of creating storages while following the discussed process.

Enterprise Structure Progress and Shipping Points

Parminder discussed the progress of the Enterprise structure, with a focus on logistics and materials management. He explained that new story locations could be assigned and created, and highlighted the creation of a purchase and sales organization, emphasizing that the latter would not be copied due to potential data issues. He also discussed the necessity of establishing shipping points for their operations. parminder explained that in cases where shipping occurs from different areas within a plant, multiple shipping points may need to be created and noted that the creation of shipping points is a role of the SD consultant.

Parminder's Report on Sales Assignments and SAP Configuration

parminder reported the completion of the shipping point creation and assignment plan, as well as the sales and distribution assignments. He discussed the setup of sales areas, which was in progress and would require more time due to the large number of sales areas. parminder also addressed the complexities of the data system, the process for handling customized T-Code, and the importance of checking if standard reports suffice before creating new ones. He emphasized the need for Velu to learn about SAP job and mastery for better understanding and discussed the completion of custom transition code and sales configuration assignments.

Assignment Next Steps and Fury Training

parminder outlined the next steps of an assignment, which included setting up S. 4 Hannah master data, checking the functioning of the Sd. Cycle, and starting the mapping of the Tm. Enterprise structure in the next session. parminder also addressed Jyoti's query about customization through Fury, advising on the similarities with the current process and emphasizing the importance of the team's Fury training. Finally, parminder took a short break before resuming the session.

Parminder's SGT 3 Material Creation and Transportation Planning

parminder discussed the creation of a finished goods material SGT_3_FGTM_01 for the SGT 3 project, emphasizing the importance of accurate material data for transportation planning and shipment volume calculations. He detailed the process of adding a material group and maintaining various aspects, including the 'ML Active' tick to avoid potential issues. parminder also highlighted the need for accurate address details for the Transportation Management process, using a customer's address to illustrate this process. He highlighted the necessity of considering other details such as postal code, city, country, region, and language.

Parminder's Company Code Data and Sales Orders

parminder led a discussion on maintaining company code data and reconciling accounts. He also covered the creation of sales orders, focusing on the necessity of determining pricing procedures and correcting issues related to shipping points. parminder further demonstrated the process of maintaining delivery and billing documents, and highlighted the need to link these with the Tm in future sessions. He also noted an ongoing issue with the account resignation, which was not resolved during this meeting.

Task Assignments and Refreshers

parminder assigned several tasks to the team, including setting up the SG cycle, creating the TMR structure, and configuring the system for future deliveries. The team was also tasked with creating a document for the TMR master data and submitting it by the end of the week. Parvez requested a refresher on creating a service entry and FSE document, which Parminder agreed to provide. There were also questions and clarifications regarding the Freight Unit and accessing deleted FUs.