PP/DS with SAP S/4HANA

English (original)

1.1 What Is Production Planning and Detailed Scheduling? SAP provides tools to support complete supply chain planning and execution, as well as integration with other processes and areas. One of the core processes within the sup- ply chain is production planning. The primary objective of production planning is to ensure that the right product is available at the right time and the right place to be delivered to customers and ensure the raw materials are available for production. Detailed scheduling supports the sequencing and scheduling of production operations by taking into consideration the available resource (machine resources and human resources) capacity and the availability of materials. In addition, detailed scheduling is used to ensure the optimal usage of resources. © 21 1.1 What Is Production Planning and Detailed Scheduling? Let’s take a closer look at each in the following sections.

עברית · תרגום מקצועי

‏SAP מספקת כלים לתמיכה בתכנון וביצוע מלאים של ה-supply chain, וכן אינטגרציה עם תהליכים ואזורים אחרים. אחד מתהליכי הליבה ב-supply chain הוא production planning. המטרה העיקרית של production planning היא להבטיח שהמוצר הנכון זמין בזמן הנכון ובמקום הנכון לאספקה ללקוחות, ולוודא שחומרי הגלם זמינים לייצור. ‏detailed scheduling תומך ברצף ובתזמון של פעולות הייצור תוך התחשבות בקיבולת ה-resource הזמינה (machine resources ו-human resources) ובזמינות החומרים. בנוסף, ‏detailed scheduling משמש להבטחת שימוש אופטימלי ב-resources.

English (original)

1.1.1 Production Planning The production planning process involves several steps. Let’s walk through the tradi- tional flow in SAP ERP, as follows: 1. Sales and operations planning (S&OP) The production planning process starts with an aggregated sales forecast in S&OP, which can be disaggregated and then transferred to demand management where it will become a concrete production plan with a planning strategy defined. 2. Master production scheduling (MPS) This production plan will be the input for MPS, which is used to plan finished prod- ucts and products using bottleneck resources. MPS will generate planned orders to cover the forecast by using different planning parameters for each material, but it won’t consider capacity restrictions. 3. Capacity leveling After the MPS execution, capacity leveling should be executed for the generated planned orders, adjusting the planned order dates and ensuring that the production plan is feasible and won’t exceed the capacity available in the work centers. 4. Material requirements planning (MRP) When all capacity issues are solved, it’s time to execute MRP to plan the remaining products. MRP will generate planned orders to produce semifinished products and purchase requisitions to procure raw materials. Even though SAP ERP offers this complete process for production planning, there are some limitations with the tools offered. For example, materials planning and capacity leveling are two separated steps: MPS or MRP will first generate planned orders with an infinite capacity, and the system will only consider finite capacity restrictions during capacity leveling. Another limitation is that MPS and MRP won’t consider the expira- tion date of material batches, so the expiration must be controlled separately. These limitations are in place because these very complex planning scenarios would con- sume additional hardware resources during the planning run and could require more time to finish it. In addition, no optimizations are available for planning the produc- tion or the resource usage on the manufacturing shop floor. SAP S/4HANA is basically an evolution of SAP ERP, and many of the older features are being redesigned or even replaced by new features. Although most of these older fea- tures are still in SAP S/4HANA, they are part of what is called the compatibility scope, which means they aren’t considered future technology and should be retired in the future. 1 Introduction to PP/DS with SAP S/4HANA 22 Note When a new SAP S/4HANA release is launched, SAP delivers a document called the sim- plification list, which describes the major changes of the new release, including the features that are part of the compatibility scope. An SAP Note linking to the simplifica- tion list can be found in Appendix A. In SAP S/4HANA, S&OP and demand management are gradually being replaced by cloud-based SAP IBP, and capacity planning is being replaced by PP/DS. Production planning in SAP S/4HANA is powered by MRP Live and forms the production planning part of PP/DS. PP/DS also offers optimization of the production plan and capacity utili- zation, including optimized sequencing of orders in the manufacturing resources.

עברית · תרגום מקצועי

תהליך ה-production planning כולל מספר צעדים. נעבור על הזרימה המסורתית ב-SAP ERP: 1. **Sales and operations planning (S&OP)** — התהליך מתחיל בתחזית מכירות מצרפית ב-S&OP, הניתנת ל-disaggregation ואז מועברת ל-demand management, שם היא הופכת ל-production plan קונקרטי עם planning strategy מוגדרת. 2. **Master production scheduling (MPS)** — ה-production plan הוא הקלט ל-MPS, המשמש לתכנון מוצרים מוגמרים ומוצרים המשתמשים ב-bottleneck resources. ‏MPS מייצר planned orders לכיסוי התחזית בעזרת planning parameters שונים לכל חומר, אך אינו מתחשב במגבלות קיבולת. 3. **Capacity leveling** — לאחר MPS, יש לבצע capacity leveling ל-planned orders שנוצרו — התאמת תאריכי ה-planned orders והבטחה שה-production plan ישים ולא יחרוג מהקיבולת הזמינה ב-work centers. 4. **Material requirements planning (MRP)** — לאחר פתרון בעיות הקיבולת, מבצעים MRP לתכנון יתר המוצרים. ‏MRP מייצר planned orders לייצור מוצרים מוגמרים-למחצה ו-purchase requisitions לרכש חומרי גלם. אף ש-SAP ERP מציע תהליך מלא זה, יש מגבלות בכלים. למשל, ‏materials planning ו-capacity leveling הם שני צעדים נפרדים: ‏MPS או MRP יוצרים תחילה planned orders בקיבולת אינסופית, והמערכת מתחשבת במגבלות finite capacity רק ב-capacity leveling. מגבלה נוספת: ‏MPS ו-MRP אינם מתחשבים ב-expiration date של material batches, ולכן ה-expiration נשלט בנפרד. מגבלות אלו קיימות כי תרחישי תכנון מורכבים מאוד אלו יצרכו hardware נוסף בריצת התכנון וידרשו זמן רב יותר. בנוסף, אין optimizations לתכנון הייצור או שימוש ה-resource ברצפת הייצור. ‏SAP S/4HANA הוא בעצם אבולוציה של SAP ERP, ורבות מהתכונות הישנות מעוצבות-מחדש או מוחלפות בחדשות. אף שרובן עדיין ב-S/4HANA, הן חלק ממה שנקרא compatibility scope — אינן נחשבות טכנולוגיה עתידית ואמורות להיגרע בעתיד. **הערה:** בהשקת גרסת S/4HANA חדשה, ‏SAP מספקת מסמך בשם simplification list המתאר את השינויים העיקריים, כולל התכונות שב-compatibility scope. ‏SAP Note המקשר ל-simplification list ב-Appendix A. ב-S/4HANA, ‏S&OP ו-demand management מוחלפים בהדרגה ב-SAP IBP מבוסס-ענן, ו-capacity planning מוחלף ב-PP/DS. ‏production planning ב-S/4HANA מונע ע"י MRP Live ומהווה את חלק ה-production planning של PP/DS. ‏PP/DS מציע גם optimization של ה-production plan וניצול הקיבולת, כולל רצף מותאם של orders ב-manufacturing resources.

English (original)

1.1.2 Detailed Scheduling After the production planning process is complete, resulting in the production propos- als for the in-house manufactured products, the next step is to identify the correct resources needed to execute the orders in the manufacturing shop floor where the detailed scheduling processes are used. The detailed scheduling tools should consider the availability of the materials for manufacturing and the available capacity of the machinery, tools, and human resources. In SAP ERP, detailed scheduling is supported in the form of capacity planning, which comprises two major features: capacity evaluation and capacity leveling. Capacity planning supports long-term rough-cut planning, medium-term planning, and short- term detailed planning. Capacity requirements are created by orders that are generated via the production planning tools, such as MPS and MRP. In addition, capacity requirements are created by networks in project systems and plant maintenance orders. The orders created by the planning tools are scheduled on the resources (also called work centers) based on the planning settings and using the routing master data. The routing master data defines the calculation of the duration for scheduling and the capacity required to execute a specific manufacturing step. After the capacity requirements are created, the capacity evaluation tool can be used to analyze the capacity load on the resources based on the available capacity. The capacity leveling tools are also used to dispatch and deallocate operations on the resources based on the underload and overload situations. For complex manufacturing scenarios, the SAP ERP capacity planning tools have chal- lenges in optimizing the capacity use of the resources and adhering to the production schedule to minimize delays in manufacturing. These complex requirements for capacity planning and detailed scheduling are addressed in the PP/DS component of SAP Advanced Planning and Optimization. © 23

עברית · תרגום מקצועי

לאחר השלמת תהליך ה-production planning, המוביל ל-production proposals למוצרים המיוצרים בבית, הצעד הבא הוא זיהוי ה-resources הנכונים לביצוע ה-orders ברצפת הייצור, שם משמשים תהליכי ה-detailed scheduling. כלי ה-detailed scheduling צריכים להתחשב בזמינות החומרים לייצור ובקיבולת הזמינה של מכונות, כלים, ו-human resources. ב-SAP ERP, ‏detailed scheduling נתמך בצורת capacity planning, הכולל שתי תכונות עיקריות: ‏capacity evaluation ו-capacity leveling. ‏capacity planning תומך ב-rough-cut planning ארוך-טווח, תכנון בינוני-טווח, ו-detailed planning קצר-טווח. ‏capacity requirements נוצרים ע"י orders שנוצרים דרך כלי ה-production planning (כגון MPS ו-MRP). בנוסף, ‏capacity requirements נוצרים ע"י networks ב-project systems ו-plant maintenance orders. ה-orders שנוצרו מתוזמנים על ה-resources (נקראים גם work centers) לפי הגדרות התכנון ובעזרת ה-routing master data. ה-routing master data מגדיר את חישוב משך הזמן לתזמון ואת הקיבולת הנדרשת לביצוע צעד ייצור ספציפי. לאחר יצירת ה-capacity requirements, ניתן להשתמש ב-capacity evaluation לניתוח עומס הקיבולת על ה-resources לפי הקיבולת הזמינה. כלי ה-capacity leveling משמשים גם ל-dispatch ו-deallocate של פעולות על ה-resources לפי מצבי underload ו-overload. לתרחישי ייצור מורכבים, לכלי ה-capacity planning של SAP ERP אתגרים במיטוב שימוש הקיבולת ובהיצמדות ל-production schedule למזעור עיכובים. דרישות מורכבות אלו מטופלות ברכיב ה-PP/DS של SAP Advanced Planning and Optimization.

English (original)

1.2 PP/DS with SAP 1.2 PP/DS with SAP To address those complex planning and scheduling scenarios, SAP created a new PP/DS tool, as mentioned previously. This tool was introduced a long time ago as part of SAP Advanced Planning and Optimization, which provides a set of advanced supply chain planning tools. Additionally, SAP Advanced Planning and Optimization could be inte- grated into one or multiple ERP systems, planning an entire supply chain together. SAP Advanced Planning and Optimization has the special dedicated SAP liveCache data- base, which was designed to handle very complex algorithms. The objective of PP/DS is to cover the demand with procurement proposals in the short-term horizon for critical products or to create an optimized production plan con- sidering various costs that may influence the production plan—storage costs, resource/work center costs, and delay penalties—and create an optimized resource schedule for the resources in which the manufacturing operations are performed. Key features in PP/DS include the following:  Production planning heuristics  Production planning optimizer  Interactive planning tools  Detailed scheduling heuristics  Detailed scheduling optimizer  Interactive detailed scheduling tools  Background planning and scheduling tools  Planning procedures  Pegging relationships  Alert Monitor PP/DS supports various manufacturing processes leveraged by many industries:  Discrete manufacturing In industries such as industrial machinery manufacturing, consumer goods, and so on, the discrete manufacturing process is leveraged in SAP ERP systems. With dis- crete manufacturing, the production steps flow through multiple workstations where activities such as assembly are performed, followed by the final product rolling off the production shop floor. In SAP ERP systems, discrete manufacturing is sup- ported by routing as the main master data object for the definition of the manufac- turing steps. The execution of the manufacturing is driven by production orders. In PP/DS, the discrete manufacturing master data and production orders are supported to arrive at an optimal production plan and an optimal schedule for the orders.  Production planning for process industries The process industry manufacturing process is used by industries such as chemicals, pharmaceuticals, and food and beverage. The manufacturing process is driven via 1 Introduction to PP/DS with SAP S/4HANA 24 material flows and processing of the input materials throughout the process to pro- duce the final product. In process industry processes, the master recipe is the pri- mary master data object to define the manufacturing process. The execution object in the ERP system is called the process order. In PP/DS, specific features such as tank planning, campaign planning, and continuous input/output planning support the process industry requirements.  Repetitive manufacturing In both discrete-based and process industry-based manufacturing, the manufactur- ing is driven by production and process orders. In repetitive manufacturing, how- ever, production is based on the rate in which the production line can produce the goods. Industries such as electronic/automobile components manufacturing, the same steps are performed repeatedly throughout a set period until the desired pro- duction quantity is achieved. So, in repetitive manufacturing, no manufacturing orders are used and the manufacturing quantity is guided by the planned orders. But the actual manufacturing will happen based on the rate of production of the manufacturing line. The requirements in repetitive manufacturing industries, such as creation of planned orders per period (shift, day, week, etc.) on specific production lines, are supported by special planning algorithms in PP/DS. PP/DS also supports certain industry-specific features, such as length-based planning required for metal industries, and model mix planning, which is widely used in the automobile industry.

עברית · תרגום מקצועי

כדי לטפל בתרחישי תכנון ותזמון מורכבים אלו, ‏SAP יצרה כלי PP/DS חדש. הכלי הוצג לפני זמן רב כחלק מ-SAP Advanced Planning and Optimization, המספק סט כלי supply chain planning מתקדמים. בנוסף, ‏SAP Advanced Planning and Optimization יכל להשתלב ב-ERP אחד או רבים, ולתכנן supply chain שלם יחד. ל-SAP Advanced Planning and Optimization מסד נתונים ייעודי SAP liveCache, שתוכנן לטפל באלגוריתמים מורכבים מאוד. מטרת ה-PP/DS היא לכסות את הביקוש עם procurement proposals באופק קצר-הטווח למוצרים קריטיים, או ליצור production plan מותאם בהתחשב בעלויות שונות העשויות להשפיע עליו — ‏storage costs, ‏resource/work center costs, ו-delay penalties — וליצור schedule מותאם ל-resources שבהם מבוצעות פעולות הייצור. תכונות מפתח ב-PP/DS: • Production planning heuristics • Production planning optimizer • Interactive planning tools • Detailed scheduling heuristics • Detailed scheduling optimizer • Interactive detailed scheduling tools • Background planning and scheduling tools • Planning procedures • Pegging relationships • Alert Monitor ‏PP/DS תומך בתהליכי ייצור שונים הממונפים ע"י תעשיות רבות: • **Discrete manufacturing** — בתעשיות כגון industrial machinery, מוצרי צריכה, וכו', תהליך ה-discrete manufacturing ממונף ב-SAP ERP. בו, צעדי הייצור זורמים דרך workstations מרובות שבהן מבוצעות פעילויות כגון assembly, ולאחריהן המוצר הסופי יוצא מרצפת הייצור. ב-SAP ERP, ‏discrete manufacturing נתמך ע"י routing כ-master data object העיקרי להגדרת צעדי הייצור. הביצוע מונע ע"י production orders. ב-PP/DS, ה-master data וה-production orders נתמכים להגעה ל-production plan ו-schedule מותאמים. • **Production planning for process industries** — תהליך ה-process industry משמש תעשיות כגון כימיקלים, פרמצבטיקה, ומזון ומשקאות. הייצור מונע דרך זרימות חומר ועיבוד חומרי הקלט לאורך התהליך לייצור המוצר הסופי. בתהליכי process industry, ה-master recipe הוא ה-master data object העיקרי להגדרת תהליך הייצור. אובייקט הביצוע ב-ERP נקרא process order. ב-PP/DS, תכונות ספציפיות כגון tank planning, ‏campaign planning, ו-continuous input/output planning תומכות בדרישות ה-process industry. • **Repetitive manufacturing** — ב-discrete וב-process industry, הייצור מונע ע"י production ו-process orders. ב-repetitive manufacturing, לעומת זאת, הייצור מבוסס על הקצב שבו קו הייצור יכול לייצר. בתעשיות כגון ייצור רכיבים אלקטרוניים/רכב, אותם צעדים מבוצעים שוב ושוב לאורך תקופה עד השגת כמות הייצור הרצויה. ב-repetitive manufacturing אין שימוש ב-manufacturing orders וכמות הייצור מונחית ע"י ה-planned orders, אך הייצור בפועל מתרחש לפי קצב הייצור של הקו. דרישות כגון יצירת planned orders לתקופה (משמרת, יום, שבוע וכו') בקווי ייצור ספציפיים נתמכות ע"י אלגוריתמי תכנון מיוחדים ב-PP/DS. ‏PP/DS תומך גם בתכונות ספציפיות-תעשייה, כגון length-based planning הנדרש לתעשיות מתכת, ו-model mix planning הנפוץ בתעשיית הרכב.

English (original)

1.2.1 SAP Advanced Planning and Optimization In this section, we’ll take a closer look at the PP/DS component of SAP Advanced Plan- ning and Optimization, see how it’s embedded in SAP S/4HANA, and walk through how PP/DS fits into SAP S/4HANA deployment and architecture. With the SAP S/4HANA 1610 release, PP/DS was made available in the SAP S/4HANA core. In addition, a side-by-side usage of SAP Advanced Planning and Optimization is possible with SAP S/4HANA as the ERP system. SAP introduced the cloud-based SAP IBP solution with capabilities such as demand planning, supply and response planning, and inventory planning, which will replace the SAP Advanced Planning and Optimization system for advanced planning and opti- mization functionalities such as demand planning and supply network planning. Therefore, the target architecture for the end-to-end planning and scheduling solution is to have SAP IBP as the demand and supply planning solution and SAP S/4HANA as the PP/DS system for critical products and components. Whether it’s SAP ERP or SAP S/4HANA, the configuration data, such as organizational structures and master data objects (e.g., material master, bill of materials [BOM], rout- ings, production version, work centers or resources, capacities, vendors, and custom- ers) are maintained in the ERP system. These data objects are transferred to the SAP Advanced Planning and Optimization system via the core interface. © 25 1.2 PP/DS with SAP Let’s walk through the SAP Advanced Planning and Optimization basics, before com- paring it to PP/DS in SAP S/4HANA (embedded PP/DS). SAP Advanced Planning and Optimization with SAP ERP In the SAP Advanced Planning and Optimization system, the processes start with demand planning, where the historical sales and consumption data is used for forecast- ing the demand. The outcome of demand planning is the constrained forecast, which is used to perform supply planning. Supply planning is executed using supply network planning, which comprises complex algorithms in the form of heuristics and the opti- mizer to plan supplies against demand. Demand planning and supply network planning are executed for mid- to long-term horizons. The data and process flow between the SAP ERP and SAP Advanced Planning and Optimization systems is shown in Figure 1.1. Figure 1.1 Planning Process and Data Flow between SAP ERP and SAP Advanced Planning and Optimization Systems For the short-term planning horizon, procurement proposals from the supply plan in supply network planning are transferred to PP/DS. Within PP/DS, the plan is refined further. Comparing the PP/DS component’s capabilities in SAP Advanced Planning and Optimi- zation with the tools available for planning in SAP ERP reveals that the basic structure behind the two solutions is similar; however, PP/DS provides advanced tools and fea- tures that aren’t available in SAP ERP, such as the following:  Materials planning and finite capacity planning  Optimization of production plan  Planning with exact times SAP ERP system SAP APO system Master data (material master, work centers, BOMs, routings, plants, customer, vendor, purchase info records, etc.) Transaction data (purchase orders, requisitions, planned and production orders, sales orders, planned independent requirements) Core Interface Production execution Master data (enhanced with SAP APO-specific fields) Demand planning Supply network planning Production planning and detailed scheduling SAP APO forecast and planning data (forecasts, planned orders, purchase requisitions, schedule line agreement releases) Material requirements planning for non-SAP APO materials/locations 1 Introduction to PP/DS with SAP S/4HANA 26  Forecast consumption with descriptive characteristics  Planning runs with multiple planning algorithms  Dynamic pegging and fixed pegging (assignment of receipt elements across BOM levels)  Planning with custom heuristics (planning algorithm that executes the planning on selected objects) Some of these features are only possible in the PP/DS component in SAP Advanced Planning and Optimization, which uses the SAP liveCache database, designed to algo- rithmically handle complex data and runtime-intensive functions. SAP liveCache is an object-based and enhanced SAP MaxDB database. SAP Advanced Planning and Optimization connects directly with SAP ERP, and data is transferred though the core interface. For each piece of master data to be transferred from SAP ERP to SAP Advanced Planning and Optimization via the core interface, you’ll need to create and activate an integration model so that the master data can be sent through the integration queues. After planning in SAP Advanced Planning and Optimi- zation, the planning results are also integrated into SAP ERP via the core interface, and any record stuck in the integration queue can lead to major integration problems between the systems or data inconsistencies. In planning scenarios where there are planning runs to be executed in different sys- tems, namely, SAP ERP and SAP Advanced Planning and Optimization, multiple plan- ning executions are involved, and a lot of dependencies are created due to the same product getting planned in multiple locations, For example, if the supply chain net- work consists of three plants—plants 1 and 3 planned in the PP/DS component in SAP Advanced Planning and Optimization and plant 2 planned in the SAP ERP system—and the product structure extends throughout these three plants, then three different plan- ning runs need to be spread across the SAP ERP and SAP Advanced Planning and Opti- mization systems. In addition, the second and third planning runs need to wait for the planning results to be transferred to SAP ERP from SAP Advanced Planning and Opti- mization and vice versa. SAP Advanced Planning and Optimization versus SAP S/4HANA Embedded PP/DS brings the PP/DS features from SAP Advanced Planning and Optimi- zation into the SAP S/4HANA system, enabling the SAP S/4HANA system to act as a comprehensive planning and scheduling solution for the short-term planning horizon. From a usability perspective, all PP/DS transactions are available within the SAP S/4HANA system, allowing end users to perform all the planning and scheduling functions in one system. With the PP/DS component in SAP Advanced Planning and Optimization, users need to switch between the SAP Advanced Planning and Optimization and SAP ERP sys- tems to accomplish the planning and scheduling tasks. In SAP S/4HANA, new SAP Fiori © 27 1.2 PP/DS with SAP apps have been introduced for detailed scheduling that work seamlessly with the SAP Fiori apps delivered for MRP Live planning. With SAP Advanced Planning and Optimization, the master data and transaction data need to be transferred between the SAP Advanced Planning and Optimization and SAP ERP systems because both systems need to be in sync in terms of master data. In addi- tion, for certain master data fields that are only relevant for SAP Advanced Planning and Optimization planning, the data is directly maintained only in the SAP Advanced Planning and Optimization system. The master data also needs to be synced up fre- quently between the SAP ERP and SAP Advanced Planning and Optimization systems to ensure that the data is consistent and that the planning results are correct in the SAP Advanced Planning and Optimization system. In SAP S/4HANA, master data maintenance is greatly simplified by maintaining only one version of data for SAP S/4HANA as well as for embedded PP/DS. For most master data objects, there is no need to create an integration model and transfer the data from SAP S/4HANA to embedded PP/DS. Master data objects such as materials and work cen- ters are maintained in SAP S/4HANA transactions and are flagged for use in advanced planning. Note Advanced planning is the term used in SAP S/4HANA to identify the objects and pro- cesses that use the PP/DS capability. The fields relevant to PP/DS fields are also exposed to the SAP S/4HANA master data objects and can be maintained in one transaction. When the data is stored in the data- base tables, it’s saved only in SAP S/4HANA tables, and data duplication is avoided wherever applicable. Similarly, transaction data such as planned independent requirements (PIRs), planned orders, production and process orders, purchase requisitions and orders, and sales orders are transferred to embedded PP/DS without any need for an active integration model. The relevant transaction data objects are marked as relevant for transfer in Cus- tomizing, and if the corresponding master data object is also marked as active for advanced planning, the transaction data is transferred to embedded PP/DS and from SAP S/4HANA, and vice versa. Because embedded PP/DS also uses SAP liveCache, the order objects need to be re-created in SAP liveCache upon transfer to embedded PP/DS. In scenarios involving multiple locations that require MRP and advanced planning, just one MRP Live planning run in SAP S/4HANA can plan all the materials and loca- tions, including those in PP/DS. There is no need to set up separate PP/DS planning runs to generate the procurement proposals for the advanced planning material loca- tions. The planning run results are synced between SAP S/4HANA and embedded PP/DS in real time, so the risk with the core interface queue failures are greatly reduced. 1 Introduction to PP/DS with SAP S/4HANA 28 Note Although most of the planning and scheduling features are available in embedded PP/DS, certain features of the PP/DS component of SAP Advanced Planning and Optimization aren’t available in embedded PP/DS. The critical simplification items are covered in the next section, and the complete list is available in SAP Note 3087008. Embedded PP/DS with SAP IBP The cloud-based SAP IBP) solution replaces the demand planning and supply network planning functionalities of the SAP SCM/SAP Advanced Planning and Optimization solution. SAP IBP also has other integrated solutions such as S&OP and inventory plan- ning. The long-term supply planning and midterm operational planning happens within SAP IBP, and the detailed production planning for the shorter planning horizon happens within embedded PP/DS. So, it’s essential to integrate the supply planning results from SAP IBP to embedded PP/DS to further fine-tune the plan and to ensure optimal scheduling of the plan. The concept of synchronous planning was introduced in SAP IBP and in embedded PP/DS to provide a flexible integration of the supply plan from SAP IBP into SAP S/4HANA and the production plan along with the optimized production scheduling results back to SAP IBP from SAP S/4HANA. The synchronous planning process will also define the responsibility of the SAP IBP and PP/DS systems in terms of the planning horizons each of the systems are responsible for. In SAP IBP, supply planning can be performed in two stages: (1) the time series–based supply planning is a bucket-oriented planning, where the supply elements are calcu- lated in periodic buckets (weekly, monthly, etc.); and (2) the SAP IBP response planning is an order-based supply planning process, where planned orders and purchase requisi- tions are created considering the lot size and selection of the appropriate source of sup- ply. Typically, the time series–based supply planning is performed for a longer planning horizon (e.g., 24 months, in weekly buckets), and the order-based response planning is performed for the midterm planning horizon (e.g., 3 months). Within the shorter planning horizon (e.g., 1 month), the response planning results from SAP IBP are fine-tuned considering the detailed planning and scheduling constraints defined in embedded PP/DS. SAP Digital Supply Chain Management, edition for SAP S/4HANA SAP Digital Supply Chain Management, edition for SAP S/4HANA, is a new offering to handle complex solution landscape requirements. For example, if your landscape con- sists of many ERP systems, including SAP ERP and SAP S/4HANA systems, to leverage PP/DS functionalities, you can only leverage them in the SAP S/4HANA systems as they © 29 1.2 PP/DS with SAP have the embedded PP/DS solution as part of the SAP S/4HANA core. For the SAP ERP systems, you still must have an SAP Advanced Planning and Optimization system in the landscape to leverage PP/DS functionalities. In addition, with your ERP system landscape transformation from SAP ERP systems to SAP S/4HANA, if you still choose to have a system landscape consisting of multiple SAP S/4HANA systems to leverage the PP/DS functionalities, the PP/DS setup—including the installation and management of SAP liveCache—needs to be performed in all those SAP S/4HANA systems. To reduce the complexity of managing each individual system with its own SAP liveCache, SAP Digital Supply Chain Management, edition for SAP S/4HANA, offers a hub solution. With this, multiple SAP ERP and/or SAP S/4HANA systems can be integrated into one SAP Digital Supply Chain Management, edition for SAP S/4HANA, system for leveraging PP/DS functionalities. Different flavors of SAP Digital Supply Chain Management, edi- tion for SAP S/4HANA, are available for solution capabilities such as SAP Extended Ware- house Management (SAP EWM) and SAP Transportation Management (SAP TM). SAP Digital Supply Chain Management, edition for SAP S/4HANA includes a key capability that supports PP/DS, called SAP S/4HANA Manufacturing for planning and scheduling. Figure 1.2 shows an example of two SAP ERP systems and one SAP S/4HANA system connected to the SAP Digital Supply Chain Management, edition for SAP S/4HANA sys- tem. Figure 1.2 Multiple ERP Systems Connected to One SAP Digital Supply Chain System for PP/DS The ERP systems are integrated to the SAP Digital Supply Chain system via the core inter- face. The master data objects, such as material masters, resources/work centers, BOMs, Planning/scheduling results from the SAP Digital Supply Chain system SAP ERP System 1 Master data Transaction data Planning/scheduling results from the SAP Digital Supply Chain system SAP ERP System 2 Master data Transaction data CIF SAP S/4HANA System 1 Planning/scheduling results from the SAP Digital Supply Chain system Master data Transaction data PP/DS planning/scheduling heuristics, optimization engines, interactive PP/DS tools, alert monitor Master data (possible to maintain/adjust data wherever applicable) SAP Digital Supply Chain Management, Edition for SAP S/4HANA – SAP S/4HANA Manufacturing for Planning and Scheduling System Transaction data PP/DS planning and scheduling results (planned orders, purchase requisitions) CIF CIF 1 Introduction to PP/DS with SAP S/4HANA 30 routings/master recipes, production versions, purchase info records, contracts, and sched- uling agreements, are transferred from the ERP systems to the SAP Digital Supply Chain system. In addition, the transaction data (e.g., sales orders, purchase orders, purchase requi- sitions, schedule line releases, planned orders, process orders, and production orders) are also transferred from the ERP systems to the SAP Digital Supply Chain system via the core interface. The planning and scheduling are performed in the SAP Digital Supply Chain sys- tem’s PP/DS component, and the results are integrated back to the corresponding ERP sys- tems. We’ll cover the setup and integration details between the ERP systems and the SAP Digital Supply Chain system in Chapter 9, Section 9.4.

עברית · תרגום מקצועי

בסעיף זה נבחן את רכיב ה-PP/DS של SAP Advanced Planning and Optimization, נראה כיצד הוא משובץ ב-S/4HANA, ונעבור על השתלבותו ב-deployment ובארכיטקטורה של S/4HANA. עם גרסת S/4HANA 1610, ‏PP/DS הפך זמין בליבת S/4HANA. בנוסף, ניתן שימוש side-by-side של SAP Advanced Planning and Optimization עם S/4HANA כמערכת ה-ERP. ‏SAP הציגה את פתרון SAP IBP מבוסס-הענן עם יכולות כגון demand planning, ‏supply and response planning, ו-inventory planning, שיחליפו את SAP Advanced Planning and Optimization לפונקציות תכנון ומיטוב מתקדמות כגון demand planning ו-supply network planning. לכן, ארכיטקטורת היעד לפתרון end-to-end היא SAP IBP כפתרון demand ו-supply planning ו-S/4HANA כמערכת ה-PP/DS למוצרים ורכיבים קריטיים. בין ב-SAP ERP ובין ב-S/4HANA, נתוני התצורה (כגון מבנים ארגוניים ו-master data objects: material master, ‏bill of materials [BOM], ‏routings, ‏production version, ‏work centers/resources, ‏capacities, ‏vendors, ו-customers) מתוחזקים במערכת ה-ERP. אובייקטים אלו מועברים ל-SAP Advanced Planning and Optimization דרך ה-core interface. **SAP Advanced Planning and Optimization עם SAP ERP:** התהליכים מתחילים ב-demand planning, שם נתוני המכירות והצריכה ההיסטוריים משמשים לחיזוי הביקוש. תוצאת ה-demand planning היא ה-constrained forecast, המשמש ל-supply planning. ‏supply planning מבוצע בעזרת supply network planning, הכולל אלגוריתמים מורכבים בצורת heuristics וה-optimizer לתכנון supplies מול demand. ‏demand planning ו-supply network planning מבוצעים לאופקים בינוני עד ארוך-טווח. זרימת הנתונים והתהליך בין SAP ERP ל-SAP Advanced Planning and Optimization ב-Figure 1.1. לאופק התכנון קצר-הטווח, ‏procurement proposals מה-supply plan ב-supply network planning מועברים ל-PP/DS. בתוך PP/DS, התוכנית מעודנת עוד. השוואת יכולות רכיב ה-PP/DS ב-SAP Advanced Planning and Optimization לכלי התכנון ב-SAP ERP מגלה שהמבנה הבסיסי דומה; אולם PP/DS מספק כלים ותכונות מתקדמים שאינם זמינים ב-SAP ERP: • ‏Materials planning ו-finite capacity planning • מיטוב ה-production plan • תכנון עם exact times • ‏Forecast consumption עם descriptive characteristics • ריצות תכנון עם מספר אלגוריתמי תכנון • ‏dynamic pegging ו-fixed pegging (הקצאת receipt elements על-פני רמות BOM) • תכנון עם custom heuristics (אלגוריתם תכנון המבצע תכנון על objects נבחרים) חלק מתכונות אלו אפשריות רק ברכיב ה-PP/DS ב-SAP Advanced Planning and Optimization, המשתמש ב-SAP liveCache, שתוכנן לטפל אלגוריתמית בנתונים מורכבים ובפונקציות עתירות-runtime. ‏SAP liveCache הוא מסד נתונים מבוסס-object ומורחב של SAP MaxDB. ‏SAP Advanced Planning and Optimization מתחבר ישירות ל-SAP ERP, והנתונים מועברים דרך ה-core interface. לכל master data להעברה מ-SAP ERP ל-SAP Advanced Planning and Optimization דרך ה-core interface, יש ליצור ולהפעיל integration model כדי שה-master data יישלח דרך ה-integration queues. לאחר התכנון, תוצאות התכנון משולבות חזרה ל-SAP ERP דרך ה-core interface, וכל רשומה תקועה ב-integration queue עלולה להוביל לבעיות אינטגרציה משמעותיות או לאי-עקביות נתונים. בתרחישי תכנון שבהם יש ריצות תכנון במערכות שונות (SAP ERP ו-SAP Advanced Planning and Optimization), מעורבות ריצות תכנון מרובות, ונוצרות תלויות רבות בשל תכנון אותו מוצר במיקומים מרובים. למשל, אם רשת ה-supply chain כוללת שלושה plants — ‏plants 1 ו-3 מתוכננים ברכיב ה-PP/DS וב-plant 2 ב-SAP ERP — ומבנה המוצר משתרע על שלושתם, אז שלוש ריצות תכנון שונות נדרשות על-פני המערכות. בנוסף, הריצות השנייה והשלישית צריכות להמתין שתוצאות התכנון יועברו בין המערכות. **SAP Advanced Planning and Optimization מול SAP S/4HANA:** ‏embedded PP/DS מביא את תכונות ה-PP/DS מ-SAP Advanced Planning and Optimization לתוך S/4HANA, ומאפשר ל-S/4HANA לפעול כפתרון תכנון ותזמון מקיף לאופק קצר-הטווח. מבחינת שמישות, כל טרנזקציות ה-PP/DS זמינות בתוך S/4HANA — משתמשי הקצה מבצעים את כל פונקציות התכנון והתזמון במערכת אחת. עם רכיב ה-PP/DS ב-SAP Advanced Planning and Optimization, המשתמשים נדרשים לעבור בין SAP Advanced Planning and Optimization ל-SAP ERP. ב-S/4HANA הוצגו אפליקציות Fiori חדשות ל-detailed scheduling העובדות חלק עם אפליקציות ה-Fiori ל-MRP Live. עם SAP Advanced Planning and Optimization, ה-master data וה-transaction data צריכים להיות מועברים בין המערכות מכיוון ששתיהן צריכות להיות מסונכרנות ב-master data. בנוסף, לשדות master data מסוימים הרלוונטיים רק ל-SAP Advanced Planning and Optimization, הנתונים מתוחזקים ישירות רק שם. ה-master data צריך להיות מסונכרן תכופות בין המערכות להבטחת עקביות ותוצאות תכנון נכונות. ב-S/4HANA, תחזוקת ה-master data מפושטת מאוד ע"י תחזוקת גרסה אחת בלבד הן ל-S/4HANA והן ל-embedded PP/DS. לרוב ה-master data objects, אין צורך ליצור integration model ולהעביר נתונים מ-S/4HANA ל-embedded PP/DS. אובייקטים כגון materials ו-work centers מתוחזקים בטרנזקציות S/4HANA ומסומנים לשימוש ב-advanced planning. **הערה:** ‏advanced planning הוא המונח ב-S/4HANA לזיהוי האובייקטים והתהליכים המשתמשים ביכולת ה-PP/DS. השדות הרלוונטיים ל-PP/DS חשופים גם ל-master data objects של S/4HANA וניתנים לתחזוקה בטרנזקציה אחת. בשמירת הנתונים בטבלאות, הם נשמרים רק בטבלאות S/4HANA, ו-duplication נמנע היכן שאפשר. בדומה, ‏transaction data כגון planned independent requirements (PIRs), ‏planned orders, ‏production ו-process orders, ‏purchase requisitions ו-orders, ו-sales orders מועברים ל-embedded PP/DS ללא צורך ב-integration model פעיל. אובייקטי ה-transaction data הרלוונטיים מסומנים כרלוונטיים להעברה ב-Customizing, ואם ה-master data object המתאים גם מסומן כפעיל ל-advanced planning, ה-transaction data מועבר. מכיוון ש-embedded PP/DS משתמש גם ב-SAP liveCache, אובייקטי ה-order צריכים להיווצר-מחדש ב-SAP liveCache בעת ההעברה. בתרחישים עם מיקומים מרובים הדורשים MRP ו-advanced planning, ריצת MRP Live אחת ב-S/4HANA יכולה לתכנן את כל החומרים והמיקומים, כולל אלו ב-PP/DS. אין צורך בריצות PP/DS נפרדות. תוצאות הריצה מסונכרנות בין S/4HANA ל-embedded PP/DS בזמן-אמת, כך שסיכוני כשל ה-core interface queue מצטמצמים מאוד. **הערה:** אף שרוב תכונות התכנון והתזמון זמינות ב-embedded PP/DS, תכונות מסוימות של רכיב ה-PP/DS ב-SAP Advanced Planning and Optimization אינן זמינות בו. פריטי ה-simplification הקריטיים מכוסים בסעיף הבא, והרשימה המלאה ב-SAP Note 3087008. **Embedded PP/DS עם SAP IBP:** פתרון SAP IBP מבוסס-הענן מחליף את פונקציות ה-demand planning וה-supply network planning של SAP SCM/SAP Advanced Planning and Optimization. ל-SAP IBP גם פתרונות משולבים כגון S&OP ו-inventory planning. ה-supply planning ארוך-הטווח וה-operational planning בינוני-הטווח מתרחשים בתוך SAP IBP, וה-production planning המפורט לאופק קצר יותר בתוך embedded PP/DS. לכן חיוני לשלב את תוצאות ה-supply planning מ-SAP IBP ל-embedded PP/DS לכוונון נוסף ולתזמון אופטימלי. המושג synchronous planning הוצג ב-SAP IBP וב-embedded PP/DS לאינטגרציה גמישה של ה-supply plan מ-SAP IBP ל-S/4HANA ושל ה-production plan יחד עם תוצאות התזמון המותאם חזרה ל-SAP IBP. תהליך ה-synchronous planning גם מגדיר את אחריות מערכות SAP IBP ו-PP/DS מבחינת אופקי התכנון. ב-SAP IBP, ‏supply planning מבוצע בשני שלבים: (1) ‏time series–based supply planning הוא תכנון bucket-oriented, שבו אלמנטי ה-supply מחושבים ב-buckets תקופתיים (שבועי, חודשי וכו'); ו-(2) ‏SAP IBP response planning הוא תהליך order-based, שבו planned orders ו-purchase requisitions נוצרים בהתחשב ב-lot size ובבחירת ה-source of supply המתאים. בד"כ ה-time series–based מבוצע לאופק ארוך יותר (למשל 24 חודשים, ב-buckets שבועיים), וה-order-based response planning לאופק בינוני (למשל 3 חודשים). באופק קצר יותר (למשל חודש), תוצאות ה-response planning מ-SAP IBP מכווננות בהתחשב במגבלות התכנון והתזמון המפורטות ב-embedded PP/DS. **SAP Digital Supply Chain Management, edition for SAP S/4HANA:** הצעה חדשה לטיפול בדרישות נוף פתרונות מורכבות. למשל, אם הנוף כולל מערכות ERP רבות (SAP ERP ו-S/4HANA), ניתן למנף PP/DS רק במערכות S/4HANA (להן embedded PP/DS כחלק מהליבה). למערכות SAP ERP, עדיין נדרשת מערכת SAP Advanced Planning and Optimization בנוף. בנוסף, בטרנספורמציית הנוף מ-SAP ERP ל-S/4HANA, אם בוחרים נוף עם מערכות S/4HANA מרובות למינוף PP/DS, הקמת ה-PP/DS — כולל התקנה וניהול של SAP liveCache — נדרשת בכל המערכות. להפחתת המורכבות בניהול כל מערכת עם SAP liveCache משלה, ‏SAP Digital Supply Chain Management, edition for SAP S/4HANA מציע פתרון hub. כך, מערכות SAP ERP ו/או S/4HANA מרובות משתלבות במערכת SAP Digital Supply Chain אחת למינוף PP/DS. גרסאות שונות זמינות ליכולות כגון SAP Extended Warehouse Management (SAP EWM) ו-SAP Transportation Management (SAP TM). היכולת התומכת ב-PP/DS נקראת SAP S/4HANA Manufacturing for planning and scheduling. ‏Figure 1.2 מציג דוגמה של שתי מערכות SAP ERP ו-S/4HANA אחת המחוברות למערכת SAP Digital Supply Chain. מערכות ה-ERP משתלבות ב-SAP Digital Supply Chain דרך ה-core interface. ה-master data objects (material masters, ‏resources/work centers, ‏BOMs, ‏routings/master recipes, ‏production versions, ‏purchase info records, ‏contracts, ו-scheduling agreements) מועברים מ-ERP. בנוסף, ה-transaction data (sales orders, ‏purchase orders, ‏purchase requisitions, ‏schedule line releases, ‏planned orders, ‏process orders, ו-production orders) מועבר דרך ה-core interface. התכנון והתזמון מבוצעים ברכיב ה-PP/DS של SAP Digital Supply Chain, והתוצאות משולבות חזרה למערכות ה-ERP. ההקמה והאינטגרציה בפרק 9, סעיף 9.4.

English (original)

1.2.2 Key Simplifications in PP/DS for SAP S/4HANA In this section, we’ll cover the key differences between the features of the PP/DS com- ponent of SAP Advanced Planning and Optimization and the embedded PP/DS fea- tures. These simplification items are dependent on the release version of SAP S/4HANA (this book is based on the on-premise release of SAP S/4HANA 2022). We’ll also cover the specific impacts of the simplification items in the relevant chapters; in this section, we cover the simplification items that aren’t covered in the other chapters. Embedded PP/DS can’t function as a planning hub. If there are multiple ERP systems, such as SAP ERP or SAP S/4HANA, in the solution landscape, the embedded PP/DS of one SAP S/4HANA system can’t act as a central planning and scheduling system for all the ERP systems in the landscape. Only the planning data that is part of an SAP S/4HANA system can be used by embedded PP/DS of the same system. Standalone SAP Advanced Planning and Optimization systems can work alongside embedded PP/DS, but the data should be segregated in a way that the same set of data isn’t planned by embedded PP/DS and the PP/DS component of SAP Advanced Planning and Optimization. A scenario in which a product location is planned in the SAP Advanced Planning and Optimization system for supply network planning and the same product location is planned in embedded PP/DS isn’t supported in the standard delivered SAP S/4HANA software; however, custom interfaces may be used to support such a scenario. Let’s walk through the key simplifications, as follows:  Production versions In the SAP ERP system, production-related master data such as BOMs and routings are created and linked via the master data object called the production version. These production versions, when transferred to the SAP Advanced Planning and Optimization systems, are created as production process models (PPMs) or as pro- duction data structures (PDSs) in the SAP Advanced Planning and Optimization sys- tem. While PPMs are based on older data models, PDSs are the new objects that can replace PPMs in SAP Advanced Planning and Optimization. However, in the SAP Advanced Planning and Optimization system, both PPMs and PDSs are supported. © 31 1.2 PP/DS with SAP In embedded PP/DS, only PDSs are supported; if you’re using PPMs in your existing SAP Advanced Planning and Optimization systems and plan to use embedded PP/DS, the usage of PDSs is mandatory. If you have any enhancements implemented for the transfer of PPM in the SAP Advanced Planning and Optimization or SAP ERP sys- tems, these need to be evaluated and adapted to the enhancements related to PDSs. We’ll cover this further in Chapter 2.  Simplified master data maintenance In SAP Advanced Planning and Optimization systems, it’s possible for local material masters and resources within SAP Advanced Planning and Optimization to be used in the PP/DS component of SAP Advanced Planning and Optimization. However, with embedded PP/DS, because one of the principal objectives is to reduce data duplication, it’s not possible to create materials and resources just in PP/DS; instead, the materials and work centers (resources) should be created in SAP S/4HANA in the corresponding transactions and should be marked for advanced planning. This will make these mate- rials and resources available in the PP/DS transaction in the SAP S/4HANA system.  MRP-based detailed scheduling In SAP Advanced Planning and Optimization, MRP-based detailed scheduling executes MRP in the ERP system (e.g., SAP ERP or SAP S/4HANA), and the PP/DS component of SAP Advanced Planning and Optimization is only used for detailed scheduling features. The orders created in the ERP system via MRP execution are transferred to the SAP Advanced Planning and Optimization system where the detailed scheduling is per- formed. After the detailed scheduling step, the new schedule with the new order dates is transferred back to the ERP system. However, with embedded PP/DS, this MRP-based detailed scheduling functionality isn’t available. After a material is activated for advanced planning, it must be planned and scheduled with embedded PP/DS.  MRP execution In the planning solution with SAP ERP and SAP Advanced Planning and Optimiza- tion systems, it’s possible to execute MRP in SAP ERP even though the material is planned by the PP/DS component of SAP Advanced Planning and Optimization. This option isn’t available in embedded PP/DS because MRP Live will always plan the advanced planning materials in PP/DS and not use the MRP algorithm in SAP ERP.  Planning areas The demand planning and supply network planning components of the SAP Advanced Planning and Optimization system use a data object called the planning area. All the demand planning and supply network planning data is stored at the planning area level. Some PP/DS functionalities, such as deployment planning in SAP Advanced Planning and Optimization, use the planning area data object as well. In embedded PP/DS, the demand planning and supply network planning compo- nents of SAP Advanced Planning and Optimization aren’t available, so the planning areas concept doesn’t exist in SAP S/4HANA, and the PP/DS component features of 1 Introduction to PP/DS with SAP S/4HANA 32 SAP Advanced Planning and Optimization that are dependent on the planning area aren’t available in SAP S/4HANA. Therefore, functionalities such as capacity reserva- tion and PP/DS deployment aren’t supported in embedded PP/DS.  Global available-to-promise (global ATP) Global ATP is a tool in SAP Advanced Planning and Optimization that can be trig- gered during the sales order creation process in the ERP system to check for the availability of the product and commit an availability date to the sales order. Simi- larly, capable-to-promise (CTP) is another availability check tool in SAP Advanced Planning and Optimization that checks for product availability; if there is no avail- ability, the CTP tool creates a temporary planned order in SAP Advanced Planning and Optimization by considering the available capacity of the resources and then proposes an availability date back to the ERP system. The global ATP and CTP tools aren’t part of embedded PP/DS, so these checks during the creation of sales orders aren’t available in SAP S/4HANA. However, for planned orders and production orders, the native available-to-promise (ATP) tool of SAP S/4HANA is integrated for the availability check of planned and production order components. If a planned order is created or converted into a production order in embedded PP/DS, the corresponding order created in SAP S/4HANA trig- gers the ATP check for the components.  Custom sort profiles In the SAP Advanced Planning and Optimization system, the order conversion and fixed pegging functionalities can use custom sort profiles to define the sequence of orders using the available order properties. These custom sort profiles are based on the global ATP functionality. Because global ATP isn’t supported in embedded PP/DS, the custom sort profiles also aren’t available in SAP S/4HANA.  Capable-to-match (CTM) CTM is another tool in the SAP Advanced Planning and Optimization system used to plan the demands in multiple levels of the supply chain finitely. This tool isn’t part of SAP S/4HANA because embedded PP/DS is no longer bundled with other SAP Advanced Planning and Optimization components such as demand planning or supply network planning.  PP/DS optimizer The PP/DS optimizer is a powerful scheduling optimizer that creates an optimized plan according to the objective functions defined for optimization. In the PP/DS component of SAP Advanced Planning and Optimization, the optimizer can create new supply elements (e.g., planned orders) if there is a supply shortage. In embedded PP/DS, on the other hand, the PP/DS optimizer can’t create planned orders; it can only schedule production orders and planned orders. © 33 1.2 PP/DS with SAP  Data When master data is transferred between the SAP Advanced Planning and Optimiza- tion and the ERP system via the core interface, there are multiple enhancement options (e.g., user exits and business add-ins [BAdIs]) available to add additional fields and to enhance the master data. Such enhancements cover material masters and classification data (classes and characteristics). If these enhancements are used in the existing SAP Advanced Planning and Optimization system, you need to adapt those to the corresponding enhancement options available in the SAP S/4HANA sys- tem. In embedded PP/DS, you can use the extensibility features to add fields to the material master so that any additional fields created in SAP Advanced Planning and Optimization can be made available in the SAP S/4HANA material master.

עברית · תרגום מקצועי

בסעיף זה נכסה את ההבדלים המרכזיים בין תכונות רכיב ה-PP/DS של SAP Advanced Planning and Optimization לתכונות embedded PP/DS. פריטי simplification אלו תלויים בגרסת S/4HANA (הספר מבוסס על גרסת on-premise של S/4HANA 2022). נכסה גם את ההשפעות הספציפיות בפרקים הרלוונטיים; כאן — הפריטים שאינם מכוסים בפרקים אחרים. ‏embedded PP/DS אינו יכול לתפקד כ-planning hub. אם יש מערכות ERP מרובות (SAP ERP או S/4HANA) בנוף, ‏embedded PP/DS של מערכת S/4HANA אחת אינו יכול לפעול כמערכת תכנון ותזמון מרכזית לכולן. רק נתוני התכנון שהם חלק ממערכת S/4HANA יכולים לשמש את ה-embedded PP/DS שלה. מערכות SAP Advanced Planning and Optimization עצמאיות יכולות לעבוד לצד embedded PP/DS, אך הנתונים צריכים להיות מופרדים כך שאותו סט נתונים אינו מתוכנן ע"י שניהם. תרחיש שבו product location מתוכנן ב-SAP Advanced Planning and Optimization ל-supply network planning ואותו location מתוכנן ב-embedded PP/DS אינו נתמך בתקן; אולם ניתן להשתמש בממשקים מותאמים. ה-simplifications המרכזיים: • **Production versions** — ב-SAP ERP, ‏master data כגון BOMs ו-routings נוצרים ומקושרים דרך ה-master data object production version. ‏production versions אלו, בהעברה ל-SAP Advanced Planning and Optimization, נוצרים כ-production process models (PPMs) או כ-production data structures (PDSs). בעוד PPMs מבוססים על מודלי נתונים ישנים, ‏PDSs הם האובייקטים החדשים שיכולים להחליפם. אולם ב-SAP Advanced Planning and Optimization, שניהם נתמכים. ב-embedded PP/DS, רק PDSs נתמכים; אם משתמשים ב-PPMs ומתכננים לעבור ל-embedded PP/DS, השימוש ב-PDSs חובה. אם יש enhancements ל-PPM, יש להעריכם ולהתאימם ל-PDSs. בפרק 2. • **Simplified master data maintenance** — ב-SAP Advanced Planning and Optimization, ניתן להשתמש ב-material masters ו-resources מקומיים בתוך הרכיב. אולם ב-embedded PP/DS, מכיוון שמטרה עיקרית היא הפחתת duplication, לא ניתן ליצור materials ו-resources רק ב-PP/DS; יש ליצורם ב-S/4HANA בטרנזקציות המתאימות ולסמנם ל-advanced planning. כך יהיו זמינים בטרנזקציית ה-PP/DS. • **MRP-based detailed scheduling** — ב-SAP Advanced Planning and Optimization, ‏MRP-based detailed scheduling מבצע MRP במערכת ה-ERP, והרכיב משמש רק ל-detailed scheduling. ה-orders שנוצרו ב-ERP מועברים, ה-detailed scheduling מבוצע, וה-schedule החדש מועבר חזרה. אולם ב-embedded PP/DS, פונקציה זו אינה זמינה. לאחר הפעלת material ל-advanced planning, יש לתכננו ולתזמנו עם embedded PP/DS. • **MRP execution** — בפתרון עם SAP ERP ו-SAP Advanced Planning and Optimization, ניתן לבצע MRP ב-SAP ERP גם אם החומר מתוכנן ע"י הרכיב. אפשרות זו אינה זמינה ב-embedded PP/DS כי MRP Live תמיד יתכנן את חומרי ה-advanced planning ב-PP/DS ולא ישתמש באלגוריתם ה-MRP של SAP ERP. • **Planning areas** — רכיבי ה-demand planning וה-supply network planning משתמשים ב-data object בשם planning area. כל הנתונים נשמרים ברמת ה-planning area. חלק מפונקציות ה-PP/DS (כגון deployment planning) משתמשות בו גם. ב-embedded PP/DS, רכיבי ה-demand וה-supply network planning אינם זמינים, ולכן מושג ה-planning areas אינו קיים ב-S/4HANA, ותכונות התלויות בו אינן זמינות. לכן capacity reservation ו-PP/DS deployment אינם נתמכים ב-embedded PP/DS. • **Global available-to-promise (global ATP)** — ‏global ATP הוא כלי ב-SAP Advanced Planning and Optimization הניתן להפעלה ביצירת sales order ב-ERP לבדיקת זמינות המוצר ולהתחייבות לתאריך זמינות. בדומה, ‏capable-to-promise (CTP) בודק זמינות; אם אין, יוצר planned order זמני בהתחשב בקיבולת הזמינה ומציע תאריך זמינות. ‏global ATP ו-CTP אינם חלק מ-embedded PP/DS. אולם ל-planned ו-production orders, כלי ה-ATP המקורי של S/4HANA משולב לבדיקת זמינות הרכיבים. אם planned order נוצר/מומר ל-production order ב-embedded PP/DS, ה-order המתאים ב-S/4HANA מפעיל את בדיקת ה-ATP. • **Custom sort profiles** — ב-SAP Advanced Planning and Optimization, ‏order conversion ו-fixed pegging יכולים להשתמש ב-custom sort profiles להגדרת רצף ה-orders. אלו מבוססים על global ATP. מכיוון שאינו נתמך ב-embedded PP/DS, גם ה-custom sort profiles אינם זמינים. • **Capable-to-match (CTM)** — כלי נוסף לתכנון finite של ביקושים במספר רמות ה-supply chain. אינו חלק מ-S/4HANA כי embedded PP/DS אינו עוד מצורף לרכיבים אחרים כגון demand planning או supply network planning. • **PP/DS optimizer** — ‏scheduling optimizer רב-עוצמה היוצר תוכנית מותאמת לפי ה-objective functions. ברכיב של SAP Advanced Planning and Optimization, ה-optimizer יכול ליצור supply elements חדשים (planned orders) אם יש מחסור. ב-embedded PP/DS, ה-optimizer אינו יכול ליצור planned orders; הוא יכול רק לתזמן production ו-planned orders. • **Data** — בהעברת master data דרך ה-core interface, יש אפשרויות enhancement רבות (user exits ו-business add-ins [BAdIs]) להוספת שדות ולהעשרת ה-master data (material masters ו-classification: classes ו-characteristics). אם משתמשים בהם ב-SAP Advanced Planning and Optimization הקיים, יש להתאימם לאפשרויות ב-S/4HANA. ב-embedded PP/DS ניתן להשתמש ב-extensibility להוספת שדות ל-material master.

English (original)

1.2.3 Deployment In this section, we’ll cover the deployment options available for PP/DS. To understand the reduced complexity of the deployment of embedded PP/DS, we’ll discuss the vari- ous deployment options available for the PP/DS component in SAP Advanced Planning and Optimization and in SAP ERP, add-on for embedded PP/DS. PP/DS with SAP Advanced Planning and Optimization When introduced, SAP Advanced Planning and Optimization was a standalone system on the Basis platform, which is now the SAP NetWeaver platform. The underlying data- base can be any database system, such as SAP HANA, Oracle, DB2, DB6, or Microsoft SQL Server (MSSQL). The SAP Advanced Planning and Optimization system requires a sepa- rate database for high-speed processing of the planning component, which is SAP live- Cache. SAP Advanced Planning and Optimization also supports the optimization of planning problems, and the optimizer server can be also connected to the SAP Advanced Planning and Optimization system for executing optimizations in the areas of supply network planning, CTM, transportation load builder, and PP/DS, among others. The opti- mizer engine software is installed in a server that is connected to the SAP Advanced Plan- ning and Optimization system via TCP/IP. The standalone SAP Advanced Planning and Optimization deployment option is depicted in Figure 1.3. SAP liveCache in SAP Advanced Planning and Optimization is loaded with the time- series data that is relevant for demand planning and supply network planning, as well as order data that is used by supply network planning and PP/DS. In addition, SAP live- Cache has an ATP time-series data object that is used by the Global ATP functionality. SAP Advanced Planning and Optimization also contains a business warehouse envi- ronment, which is primarily used by the demand planning component of the SAP Advanced Planning and Optimization system to store historical data that is used in the forecasting process. 1 Introduction to PP/DS with SAP S/4HANA 34 Figure 1.3 SAP Advanced Planning and Optimization Standalone Deployment Model As Figure 1.4 shows, the SAP Advanced Planning and Optimization system running on the SAP HANA database can use SAP liveCache, which is built into the SAP HANA data- base. This eliminates the requirement to have separate database system maintenance for SAP liveCache. Figure 1.4 SAP Advanced Planning and Optimization Standalone Deployment on an SAP HANA Database The standalone SAP Advanced Planning and Optimization deployment model is rec- ommended for large and extra-large installations that require a lot of hardware resources to execute the SAP Advanced Planning and Optimization planning pro- cesses. SAP liveCache Any Database; Only SAP HANA Database for SAP S/4HANA Any Database SAP MaxDB Database SAP SCM Optimizer Engine SAP Supply Chain Management – SAP Advanced Planning and Optimization System ERP System (SAP ERP or SAP S/4HANA) ERP System (SAP ERP or SAP S/4HANA) Any Database; Only SAP HANA Database for SAP S/4HANA SAP HANA Database including SAP liveCache SAP SCM Optimizer Engine SAP Supply Chain Management – SAP Advanced Planning and Optimization System © 35 1.2 PP/DS with SAP As of SAP SCM 7.0 EHP 3, SAP Advanced Planning and Optimization can be deployed as an add-on to the SAP ERP system. This add-on is installed on the existing SAP ERP sys- tem, and the SAP Advanced Planning and Optimization functionalities are provided with the activation of the switch framework. In addition, the base configuration for the SAP Advanced Planning and Optimization components is in the form of business con- figuration sets. Upon activation of the SAP Advanced Planning and Optimization switch and the business configuration sets installation, the SAP Advanced Planning and Optimization features are available in the SAP ERP system. The services parts plan- ning component and the maintenance and service planning component of SAP Advanced Planning and Optimization aren’t available in the SAP Advanced Planning and Optimization on SAP ERP add-on. This deployment option is shown in Figure 1.5. Figure 1.5 SAP Advanced Planning and Optimization as an Add-On to an SAP ERP System SAP Advanced Planning and Optimization and the SAP ERP version reside in one SAP system and share a common SAP NetWeaver platform. When upgrading SAP Advanced Planning and Optimization and/or SAP ERP to a newer version or EHP, there are tech- nical dependencies; the combination of SAP NetWeaver, SAP Advanced Planning and Optimization, and SAP ERP versions must be released for SAP Advanced Planning and Optimization add-on deployment. For example, updating the SAP Advanced Planning and Optimization add-on to a newer version may require SAP NetWeaver to be updated and require SAP ERP to be updated so that all components are on compatible versions. The SAP ERP add-on deployment model is recommended for small and medium deployments. As the same hardware is shared by SAP ERP and SAP Advanced Planning Any Database SAP SCM Optimizer Engine SAP liveCache SAP MaxDB Database SAP APO Add-On ERP System (SAP ERP) 1 Introduction to PP/DS with SAP S/4HANA 36 and Optimization processes, the system should be sufficiently sized to cover the addi- tional load. For SAP ERP systems running on the SAP HANA database, the SAP Advanced Planning and Optimization add-on also has embedded PP/DS features and simplifications related to master data and the core interface. This deployment option is shown in Fig- ure 1.6. Figure 1.6 SAP ERP, Add-On for Embedded PP/DS This option of the SAP ERP, add-on for embedded production planning and detailed scheduling system is available from the SAP SCM 7.0 EHP 4 version and SAP ERP 6.0 EHP 8 version. This option also supports MRP Live features and SAP Fiori apps. Embedded PP/DS SAP S/4HANA 1610 introduced embedded PP/DS. No other features of the SAP Advanced Planning and Optimization system are part of the SAP S/4HANA system. A standalone deployment of the SAP Advanced Planning and Optimization system can be used along with the SAP S/4HANA system. However, if embedded PP/DS is used, the same data can’t be used for planning in the SAP Advanced Planning and Optimization system. Integration of orders generated out of standalone SAP Advanced Planning and Optimization systems can’t be integrated into embedded PP/DS. Figure 1.7 shows the embedded PP/DS deployment option. In embedded PP/DS, SAP liveCache is also embedded in the SAP HANA database on which the SAP S/4HANA system runs. It’s recommended to install the optimizer engine in a separate server and connect to SAP S/4HANA using TCP/IP. The detailed architec- ture of embedded PP/DS is covered in the next section. SAP SCM Optimizer Engine SAP HANA Database including SAP liveCache ERP System (SAP ERP) SAP APO Add-On + Embedded PP/DS © 37 1.2 PP/DS with SAP Figure 1.7 Embedded PP/DS Deployment The new SAP S/4HANA core architecture sets the base for the feature innovations and simplification of the data, processes, and usability. The SAP S/4HANA platform is criti- cal for enabling Industry 4.0 features in the supply chain to enable and integrate intel- ligent technologies such as the Internet of Things (IoT) and machine learning. Embedded PP/DS leverages the power of SAP S/4HANA for simplifying the data, usabil- ity, and simplifications in the core interface. As a target architecture, deployment of SAP S/4HANA, including the activation of embed- ded PP/DS integrated with cloud-based SAP IBP, should be targeted for the end-state architecture of the SAP Digital Supply Chain solution. The standalone SAP Advanced Planning and Optimization solution is currently supported with SAP S/4HANA, but all the future innovations for the planning and scheduling solutions will be delivered in SAP IBP and SAP S/4HANA. SAP Digital Supply Chain Management, edition for SAP S/4HANA For complex system and solution architecture requirements, including multiple ERP systems such as SAP ERP and SAP S/4HANA in the landscape, deployment of SAP Digi- tal Supply Chain Management, edition for SAP S/4HANA manufacturing can be con- sidered to simplify the need to maintain and run multiple PP/DS systems in the landscape. As shown in Figure 1.8, SAP HANA integrated in SAP liveCache will be part of the SAP Digital Supply Chain system, and all the satellite ERP systems, including SAP S/4HANA systems, will integrate into the SAP Digital Supply Chain system. SAP S/4HANA System SAP HANA Database including SAP liveCache SAP SCM Optimizer Engine PP/DS for SAP S/4HANA 1 Introduction to PP/DS with SAP S/4HANA 38 Figure 1.8 Deployment of SAP Digital Supply Chain Management, Edition for SAP S/4HANA Figure 1.9 shows the transformation of features and functionality in SAP SCM. The SAP ERP and SAP Advanced Planning and Optimization solution capabilities are compared to the SAP S/4HANA and SAP IBP solution capabilities. Figure 1.9 SAP SCM Solution Transformation Any Database SAP SCM Optimizer Engine ERP System (SAP ERP) ERP System (SAP S/4HANA) SAP HANA Database including SAP liveCache SAP Digital Supply Chain Management, Edition for SAP S/4HANA – SAP S/4HANA Manu- facturing for Planning and Scheduling SAP HANA Database Supply Network Planning Process Sales and Operations Planning Supply Planning Inventory Optimization MRP Detailed Production Planning and Scheduling Capacity Planning Production Planning/ Detailed Scheduling Visibility Demand Planning Forecasting/Demand Planning Order Promising Allocation Planning and Global ATP Order Management Supply Chain Infocenter SAP ERP SAP APO SAP ERP Sales and Operations Planning Demand Management SAP S/4HANA MRP Live and PP/DS MRP Live and PP/DS Advanced Order Promising SAP IBP SAP IBP for Sales and Operations Planning SAP IBP for Inventory SAP Supply Chain Control Tower SAP IBP for Demand SAP IBP for Response and Supply MRP Live SAP Fiori Apps Demand Management DDMRP SAP IBP for Response and Supply © 39 1.2 PP/DS with SAP

עברית · תרגום מקצועי

בסעיף זה נכסה את אפשרויות ה-deployment ל-PP/DS. להבנת המורכבות המופחתת של embedded PP/DS, נדון באפשרויות ה-deployment השונות לרכיב ב-SAP Advanced Planning and Optimization וב-SAP ERP, add-on for embedded PP/DS. **PP/DS עם SAP Advanced Planning and Optimization:** בהצגתו, ‏SAP Advanced Planning and Optimization היה מערכת standalone על פלטפורמת ה-Basis (כיום SAP NetWeaver). מסד הנתונים הבסיסי יכול להיות כל מערכת (SAP HANA, ‏Oracle, ‏DB2, ‏DB6, או Microsoft SQL Server [MSSQL]). המערכת דורשת מסד נתונים נפרד לעיבוד מהיר — ‏SAP liveCache. היא תומכת גם ב-optimization, וניתן לחבר optimizer server לביצוע optimizations באזורי supply network planning, ‏CTM, ‏transportation load builder, ו-PP/DS. תוכנת ה-optimizer engine מותקנת בשרת המחובר דרך TCP/IP. אפשרות ה-standalone ב-Figure 1.3. ‏SAP liveCache טעון בנתוני time-series הרלוונטיים ל-demand planning ו-supply network planning, וכן בנתוני order המשמשים supply network planning ו-PP/DS. בנוסף, ל-SAP liveCache יש ATP time-series data object המשמש את Global ATP. ‏SAP Advanced Planning and Optimization כולל גם סביבת business warehouse, המשמשת בעיקר את רכיב ה-demand planning לאחסון נתונים היסטוריים בתהליך החיזוי. כפי שב-Figure 1.4, מערכת הרצה על מסד SAP HANA יכולה להשתמש ב-SAP liveCache המובנה ב-SAP HANA — מבטל את הצורך בתחזוקת מסד נפרד. מודל ה-standalone מומלץ להתקנות גדולות וגדולות-מאוד הדורשות hardware רב. מ-SAP SCM 7.0 EHP 3, ניתן לפרוס SAP Advanced Planning and Optimization כ-add-on ל-SAP ERP. ה-add-on מותקן על SAP ERP הקיים, והפונקציות מסופקות עם הפעלת ה-switch framework. בנוסף, התצורה הבסיסית בצורת business configuration sets. עם הפעלת ה-switch והתקנת ה-business configuration sets, התכונות זמינות ב-SAP ERP. רכיבי services parts planning ו-maintenance and service planning אינם זמינים ב-add-on זה. אפשרות זו ב-Figure 1.5. ‏SAP Advanced Planning and Optimization וגרסת ה-SAP ERP שוכנים במערכת אחת וחולקים פלטפורמת SAP NetWeaver משותפת. בשדרוג לגרסה/EHP חדשים, יש תלויות טכניות; שילוב גרסאות SAP NetWeaver, ‏SAP Advanced Planning and Optimization, ו-SAP ERP חייב להיות משוחרר ל-add-on deployment. מודל ה-SAP ERP add-on מומלץ לפריסות קטנות ובינוניות. מכיוון שאותו hardware משותף, המערכת צריכה להיות ממודדת מספיק לעומס הנוסף. למערכות SAP ERP הרצות על SAP HANA, ל-add-on יש גם תכונות embedded PP/DS ו-simplifications של master data וה-core interface. אפשרות זו ב-Figure 1.6. אפשרות זו של SAP ERP, add-on for embedded PP/DS זמינה מ-SAP SCM 7.0 EHP 4 ו-SAP ERP 6.0 EHP 8. היא תומכת גם ב-MRP Live ובאפליקציות Fiori. **Embedded PP/DS:** ‏SAP S/4HANA 1610 הציג embedded PP/DS. אין תכונות SAP Advanced Planning and Optimization אחרות בו. ניתן להשתמש ב-deployment standalone של SAP Advanced Planning and Optimization לצד S/4HANA. אולם אם משתמשים ב-embedded PP/DS, אותם נתונים לא יכולים לשמש לתכנון ב-SAP Advanced Planning and Optimization. אינטגרציית orders שנוצרו במערכות standalone אינה אפשרית ל-embedded PP/DS. ‏Figure 1.7 מציג אפשרות זו. ב-embedded PP/DS, ‏SAP liveCache גם משובץ במסד SAP HANA שעליו רצה S/4HANA. מומלץ להתקין את ה-optimizer engine בשרת נפרד ולחבר דרך TCP/IP. ארכיטקטורת הליבה החדשה של S/4HANA מציבה בסיס לחדשנות ולפישוט הנתונים, התהליכים, והשמישות. הפלטפורמה קריטית לאפשור תכונות Industry 4.0 ב-supply chain ולשילוב טכנולוגיות חכמות כגון Internet of Things (IoT) ו-machine learning. ‏embedded PP/DS ממנף את עוצמת S/4HANA לפישוט הנתונים, השמישות, וה-core interface. כארכיטקטורת יעד, יש לכוון ל-deployment של S/4HANA כולל הפעלת embedded PP/DS המשולב עם SAP IBP מבוסס-ענן. פתרון ה-standalone נתמך כיום עם S/4HANA, אך כל החדשנות העתידית תסופק ב-SAP IBP וב-S/4HANA. **SAP Digital Supply Chain Management, edition for SAP S/4HANA:** לדרישות ארכיטקטורה מורכבות, כולל מערכות ERP מרובות, ניתן לשקול deployment של SAP Digital Supply Chain Management, edition for SAP S/4HANA manufacturing לפישוט הצורך בתחזוקת מערכות PP/DS מרובות. כפי שב-Figure 1.8, ‏SAP HANA המשולב ב-SAP liveCache יהיה חלק ממערכת SAP Digital Supply Chain, וכל מערכות ה-ERP הלוויניות (כולל S/4HANA) ישתלבו בה. ‏Figure 1.9 מציג את טרנספורמציית התכונות ב-SAP SCM — השוואת יכולות SAP ERP ו-SAP Advanced Planning and Optimization מול S/4HANA ו-SAP IBP.

English (original)

1.2.4 Architecture SAP S/4HANA has a new, simplified architecture to remove any redundancies in tech- nologies, applications, and data. In this section, we’ll cover the general architecture of the SAP S/4HANA system and the architecture of embedded PP/DS. SAP S/4HANA simplified the architecture of the previous ERP versions. The principle of one is applied in the new architecture, which simplifies any duplicate functionalities and the need to save the same data in multiple tables for performance purposes. From a technical perspective, the multiple frameworks available with the ERP systems to realize functionality have been simplified in SAP S/4HANA. In the ERP systems running on any database, to optimize the performance of the appli- cations, the data is aggregated at different characteristics levels of the data, such as periods (daily, weekly, monthly), and aggregated at certain organizational levels. How- ever, with the power of SAP HANA, these aggregations can be performed on the fly, and there is no need to create redundant data in the database tables. With SAP S/4HANA, the applications can use the SAP HANA database to perform complex calculations. An example of how the inventory data storage is simplified in the SAP S/4HANA architec- ture is shown in Figure 1.10. In this example, the data is stored in more than 25 tables in SAP ERP systems, whereas this is simplified to just 2 tables in the SAP S/4HANA system. Figure 1.10 Simplification in the SAP S/4HANA Inventory Management Data Model Architecture Another simplification in the architecture from the usability perspective is in the user interface (UI). For many business process areas, there are new, enhanced role-based MSTQH MARD MARC MSTEH MSTBH MSSQH MSSAH MSPRH MSTQ MSTE MSTB MSSQ MSSA MSPR MSLB MSKU MSKA MKOL MCHB MKPF MSEG Aggregated data tables Document MATDOC MATDOC_ EXTRACT Historical data tables SAP ERP SAP S/4HANA Master data tables with inventory data MSLBH MSKUH MSKAH MKOLH MCHBH MARDH MARCH 1 Introduction to PP/DS with SAP S/4HANA 40 SAP Fiori apps delivered with the SAP S/4HANA system that provide the end user with a unified and seamless UI irrespective of the device being used. SAP S/4HANA also has embedded analytics to bring in real-time transaction data and provide context to the transaction data with the master data within the transactional SAP Fiori apps. In addition, there are standalone SAP Fiori analytics apps that use the core data service (CDS) views to process the data during runtime and to provide power- ful analytics. The SAP S/4HANA architecture also makes the platform future-ready for innovations and integration to other cloud solutions. To enable the simplifications in terms of data, usability, analytics, and future readiness, the technical architecture of the SAP S/4HANA system is designed as shown in Figure 1.11. The SAP HANA database layer consists of the database tables, and the CDS views enable simplified access to combined data from mul- tiple tables. The SAP S/4HANA layer contains the transactional and analytical business logic, as well as Enterprise Search, which simplifies and enhances the search capability in the SAP S/4HANA system. SAP Gateway is the communication layer between the SAP S/4HANA system and the SAP Fiori UI. The SAP Gateway layer contains all the technical artifacts to bring the data from the SAP S/4HANA system to the SAP Fiori apps. Figure 1.11 SAP S/4HANA Technical Architecture In terms of data model simplifications in master data, integration of master data and transaction data, and usability simplifications, the simplicity and feature-rich SAP S/4HANA architecture is also used by embedded PP/DS. In addition to the SAP S/4HANA core, which now is embedded with the PP/DS application functionalities, PP/DS also requires SAP liveCache to execute the complex planning and scheduling algorithms. SAP liveCache is part of the SAP HANA database in the SAP S/4HANA architecture. Figure 1.12 shows the difference between the standalone SAP Advanced Planning and Optimization and SAP ERP solution architecture and that of embedded PP/DS. Database Tables SAP HANA SAP S/4HANA Transactional Logic Analytics Enterprise Search SAP Fiori SAP Fiori Launchpad Search SAP Fiori Apps CDS Views SAP Gateway © 41 1.2 PP/DS with SAP Figure 1.12 Simplified Embedded PP/DS Architecture Embedded PP/DS has a simplified master data architecture. The master data is main- tained in SAP S/4HANA and is visible and available for embedded PP/DS. The material master and work center are activated for advanced planning, which makes it available for embedded PP/DS. For the resource master data, the corresponding SAP liveCache time stream is also generated. For PP/DS master data, such as the PDS, a generation report is provided, which will gen- erate and save the PDS in the PP/DS tables by using the remote function call (RFC) within the same SAP S/4HANA system. The business partner data (customers and ven- dors) and the organizational structure data (plant, shipping points, and MRP areas) are transferred to embedded PP/DS using a generation report. The variant configuration classes created in SAP S/4HANA are available for embedded PP/DS without the need to create any specific integration model. For master data elements such as purchase info records, contracts, and scheduling agreements, an integration model is required to generate the external procurement relationship master data in embedded PP/DS. In addition, the characteristics-dependent planning (CDP) class type, which is specific to embedded PP/DS and not relevant for SAP S/4HANA, also requires an integration model for the transfer to embedded PP/DS. The transaction data created in SAP S/4HANA is also transferred to embedded PP/DS and saved in SAP liveCache and in the mapping tables to ensure the consistency of the data in SAP S/4HANA and SAP liveCache. Similarly, the planning data created in embed- ded PP/DS is saved in SAP liveCache and sent to SAP S/4HANA. The transaction data includes planned orders and production orders for in-house manufacturing, purchase requisitions, purchase orders, scheduling agreement releases for external procure- ment, sales orders, forecast elements, and PIRs. The data architecture for most com- monly used master and transaction data is shown in Figure 1.13. Sales order entry MRP run and constrained planning Interactive planning Release to production Production execution Monitoring and controlling SAP ERP and SAP APO SAP APO – PP/DS SAP liveCache CIF SAP HANA platform including SAP liveCache Master data One MRP CIF ERP PP/DS SAP S/4HANA SAP GUI SAP Fiori/Mobile/SAP GUI SAP ERP on SAP HANA or any Database 1 Introduction to PP/DS with SAP S/4HANA 42 Figure 1.13 Embedded PP/DS Data Architecture The SAP Digital Supply Chain system is similar to an embedded PP/DS system in terms of the technical architecture, but it only runs the PP/DS processes, and all the other manufacturing and logistics processes are executed in the connected ERP systems, which are integrated to the SAP Digital Supply Chain system via the core interface.

עברית · תרגום מקצועי

ל-S/4HANA ארכיטקטורה חדשה ומפושטת להסרת redundancies בטכנולוגיות, יישומים, ונתונים. בסעיף זה נכסה את הארכיטקטורה הכללית של S/4HANA ושל embedded PP/DS. ‏S/4HANA פישט את הארכיטקטורה של גרסאות ה-ERP הקודמות. עקרון ה-principle of one מיושם בארכיטקטורה החדשה, מפשט פונקציות כפולות ואת הצורך לשמור אותם נתונים בטבלאות מרובות. מבחינה טכנית, ה-frameworks המרובים שהיו ב-ERP פושטו ב-S/4HANA. במערכות ERP הרצות על כל מסד נתונים, למיטוב ביצועים, הנתונים מצרפיים ברמות characteristics שונות (תקופות: יומי, שבועי, חודשי) וברמות ארגוניות מסוימות. אולם בעוצמת SAP HANA, אגרגציות אלו מבוצעות on the fly ואין צורך בנתונים מיותרים. עם S/4HANA, היישומים יכולים להשתמש ב-SAP HANA לחישובים מורכבים. דוגמה לפישוט אחסון נתוני המלאי ב-Figure 1.10: הנתונים נשמרים ביותר מ-25 טבלאות ב-SAP ERP, ומפושטים ל-2 טבלאות בלבד ב-S/4HANA. פישוט נוסף בארכיטקטורה מבחינת שמישות הוא ב-user interface (UI). לאזורי תהליך עסקיים רבים, יש אפליקציות Fiori מבוססות-role חדשות ומשופרות המספקות UI מאוחד וחלק ללא קשר למכשיר. ל-S/4HANA יש גם embedded analytics להבאת transaction data בזמן-אמת ולמתן הקשר עם ה-master data בתוך אפליקציות Fiori טרנזקציוניות. בנוסף, יש אפליקציות Fiori analytics עצמאיות המשתמשות ב-core data service (CDS) views לעיבוד הנתונים בזמן-ריצה ולמתן analytics רב-עוצמה. הארכיטקטורה גם הופכת את הפלטפורמה ready-לעתיד לחדשנות ולשילוב עם פתרונות ענן. כדי לאפשר את הפישוטים (נתונים, שמישות, analytics, ומוכנות עתידית), הארכיטקטורה הטכנית מעוצבת כב-Figure 1.11. שכבת מסד ה-SAP HANA כוללת את הטבלאות, וה-CDS views מאפשרים גישה מפושטת לנתונים משולבים ממספר טבלאות. שכבת ה-S/4HANA כוללת את ה-business logic הטרנזקציוני וה-analytical, וכן Enterprise Search המפשט ומעשיר את יכולת החיפוש. ‏SAP Gateway היא שכבת התקשורת בין S/4HANA ל-Fiori UI, ומכילה את כל ה-artifacts הטכניים להבאת הנתונים לאפליקציות Fiori. מבחינת פישוטי data model ב-master data, אינטגרציה של master ו-transaction data, ופישוטי שמישות, הארכיטקטורה הפשוטה ועתירת-התכונות משמשת גם את embedded PP/DS. בנוסף לליבת ה-S/4HANA (המשובצת כעת בפונקציות PP/DS), ‏PP/DS דורש גם SAP liveCache לביצוע אלגוריתמי התכנון והתזמון המורכבים. ‏SAP liveCache הוא חלק ממסד SAP HANA. ‏Figure 1.12 מציג את ההבדל בין ארכיטקטורת ה-standalone של SAP Advanced Planning and Optimization ו-SAP ERP לבין זו של embedded PP/DS. ל-embedded PP/DS ארכיטקטורת master data מפושטת. ה-master data מתוחזק ב-S/4HANA וגלוי וזמין ל-embedded PP/DS. ה-material master וה-work center מופעלים ל-advanced planning, מה שהופך אותם זמינים. ל-resource master data, נוצר גם ה-SAP liveCache time stream המתאים. ל-PP/DS master data (כגון PDS), מסופק generation report היוצר ושומר את ה-PDS בטבלאות ה-PP/DS בעזרת remote function call (RFC) בתוך אותה מערכת S/4HANA. נתוני ה-business partner (customers ו-vendors) ונתוני המבנה הארגוני (plant, ‏shipping points, ו-MRP areas) מועברים ל-embedded PP/DS בעזרת generation report. ה-variant configuration classes שנוצרו ב-S/4HANA זמינים ל-embedded PP/DS ללא integration model. לאלמנטי master data כגון purchase info records, ‏contracts, ו-scheduling agreements, נדרש integration model ליצירת ה-external procurement relationship master data ב-embedded PP/DS. בנוסף, ה-characteristics-dependent planning (CDP) class type, הספציפי ל-embedded PP/DS, גם דורש integration model. ה-transaction data שנוצר ב-S/4HANA מועבר גם ל-embedded PP/DS ונשמר ב-SAP liveCache ובטבלאות ה-mapping להבטחת עקביות הנתונים. בדומה, נתוני התכנון שנוצרו ב-embedded PP/DS נשמרים ב-SAP liveCache ונשלחים ל-S/4HANA. ה-transaction data כולל planned orders ו-production orders לייצור-בית, ‏purchase requisitions, ‏purchase orders, ‏scheduling agreement releases לרכש חיצוני, ‏sales orders, אלמנטי forecast, ו-PIRs. ארכיטקטורת הנתונים ב-Figure 1.13. מערכת ה-SAP Digital Supply Chain דומה ל-embedded PP/DS מבחינה טכנית, אך מריצה רק את תהליכי ה-PP/DS, וכל תהליכי הייצור והלוגיסטיקה האחרים מבוצעים במערכות ה-ERP המחוברות, המשתלבות דרך ה-core interface.

English (original)

1.3 Summary In this chapter, we introduced the basics of production planning, detailed scheduling, and deployment options, as well as the architecture of the PP/DS component for SAP Advanced Planning and Optimization, embedded PP/DS, and the SAP Digital Supply Chain Management, edition for SAP S/4HANA (specifically, SAP S/4HANA Manufactur- ing for planning and scheduling) solutions. We also covered the evolution of the PP/DS architecture in the SAP systems and the embedded PP/DS data architecture in detail. As we discussed in this chapter, the cloud-based SAP IBP system, embedded PP/DS, and SAP Digital Supply Chain PP/DS will eventually replace the on-premise SAP Advanced Planning and Optimization system for the demand, supply planning, and PP/DS func- tionalities. In the next chapter, we’ll cover the critical master data objects required to operate embedded PP/DS for executing the PP/DS processes. Transaction data: in-house manufacturing, external procurement orders, sales orders, forecasts, PIRs PP/DS-specific master data External procurement relationships CDP classes SAP liveCache Resource time stream In-house manufacturing, external procurement orders, sales orders, forecasts, PIRs ERP side PP/DS side SAP S/4HANA Mapping tables Simplified master data (material master, resources, BOM, routing, production version, business partner, classes (VC), classes (CDP), characteristics, purchase info records, contracts) PDS, PP/DS locations Generation reports Integration models ©

עברית · תרגום מקצועי

בפרק זה הצגנו את יסודות ה-production planning, ‏detailed scheduling, ואפשרויות ה-deployment, וכן את הארכיטקטורה של רכיב ה-PP/DS ל-SAP Advanced Planning and Optimization, ‏embedded PP/DS, ופתרונות SAP Digital Supply Chain Management, edition for SAP S/4HANA (במיוחד SAP S/4HANA Manufacturing for planning and scheduling). כיסינו גם את אבולוציית ארכיטקטורת ה-PP/DS ואת ארכיטקטורת הנתונים של embedded PP/DS לפרטים. כפי שדנו, מערכת SAP IBP מבוססת-הענן, ‏embedded PP/DS, ו-SAP Digital Supply Chain PP/DS יחליפו בסופו של דבר את מערכת SAP Advanced Planning and Optimization ה-on-premise לפונקציות ה-demand, ‏supply planning, ו-PP/DS. בפרק הבא נכסה את אובייקטי ה-master data הקריטיים הנדרשים להפעלת embedded PP/DS לביצוע תהליכי ה-PP/DS.