2.0 Business Process

Capture the business process that the application supports . This can be describe through a process diagram or a business capability model

Material in transit (Inbound) (ABMMIM07*)

The provider creates a key like the inventory model using plant, material, batch and date reference for summing all inbound and outbound quantity/ values linked with the in transit financial process.

AMDP

• Calendar date - The date used in GIT table is the sy-datum from snapshot, in the business layer we changed it because this snapshot corresponds the previous working day.
• Plant - For inbound process, if the plant is not filled, the process get data from shipping plant.
• Controlling Area - If the controlling area is null, get the data from the corresponding attribute of "company code" (c_compcde);
• GBU - Get the data from the attribute of "Sub-activity 2" (c_subact2);
• Material conversion - If the corresponding material and unit of measure is not convertible into 'KG' according to the DSO UOMCMAT2, the object is flagged.
• Once the GIT table is daily snapshot, the key figure uses aggregation last position based on calday and the recursive is used to identify if some material x plant x batch are not available anymore in the current date or end of month. 

3.0 Application Feature Overview

Information about the existent Workbooks and the respective BW queries.

4.0 Business Objects

This section should contain a table with the business objects used in the reports and the link for the Data Catalog.

Data Catalog Link: XXXXXX

5.0 Functional Specification

5.1 General Data/Calculations 

This section will approach the concepts/definitions that will be used in all the reports and required to understand the data from the reports.

Could be specific fields, closing activities, additional information to work and understand the reports.

Functional and Technical rules on Workbench + Reporting

MM-IM: SMOG (HANA Ext. View) (BW_QRY_CPIMMM03*_0001)

BW query with filter to get only the 10 GBUs used in the SAC dashboard, material and plants not obsoletes and with the valuation class corresponding to relevant according to the business units.

• 0CALYEAR was defined with only 2 years per time in a fix value because query as external view doesn't allow HANA or ABAP variables.

• The provider CPMMIM03R provides two queries because of the volume of data processed by the total stock in Rhodia model; BW_QRY_CPIMMM03R_0002 (only CS) and BW_QRY_CPIMMM03R_0001 (other GBUs).

Calc. view for position of last month (CV_MM_IM_ABMMIM05*_M1)

Calculation view based on the query bw_qry_cpimmm03*_0001, filtering the previous month and the situations where the batch expire date or manufacture date from batch is not initial. The data come back to BW by the datasource CV_MM_IM_ABMMIM05*_M1 (WBP_HANAIV).

MM-IM: SMOG Evolution (Only Sotck Type) (BW_QRY_CPIMMM01_0011)

BW query with filter to get only the stockt type 'C', 'D' or 'E', the 10 GBUs used by the SAC dashboard, material and plants not obsoletes and with the valuation class corresponding to relevant according to the business units.

The are two DTP when retrieving data to the provider ABMMIM06*, M-3 → M-1 and M-6 → M-4. 

Material Movement - SMOG (ABMMIM06*)

The provider concatenate the results respecting the sequence batches blocked, obsolete and slow moving, if the same batch is classified in more than one condition.

AMDP

• Blocked - All batch with the stock type equal 'C', 'D' or 'E'
• Obsolete - If the last day of respective month of the load is greater than batch expiry date
• Slow moving - If the last day of respective month minus the batch manufacture date is bigger than 365 days
• Batch aging - According to the difference of days for the previous 2 classifications, it was created the aging 0 - 90 days, 90-120 days, 121 - 360 days, 361 - 720 days and greater than 720 days.

Material Movement - SMOG (ABMMIM06*) Recursive Load

Once the provider concatenates the results respecting the sequence batches blocked, obsolete and slow moving with the corresponding values converted into EUR and quantities in VKG, the objects are order with the differences about the in and out results, split into I (IN) when the values and quantities are assigned at the first time according to the key or they rose, we keep without flag when the values don't change among the months or the difference between IN and the results from the month before, beyond that we classify as O (outbound) when the results reduce or they are not available anymore with the corresponding key in the sequent month.

AMDP

• The rules to assign IN and OUT is done at this level in the end routine comparing values for the same key with the month treated in the load with the month before and after.

Data loading

Monthly process chain loaded at the day 05 for getting the data from previous month.

PC_MMIM_19 - MM: IM - M - SMOG Rhodia

PC_MMIM_20 - MM: IM - M - SMOG Solvay

The INIT process has a specific view on top of the ztest query Rhodia (ztest_cv_qry_cpmmim03r_0003) and Solvay (ztest_cv_qry_cpmmim03s_0002). They are ztest as an alternative to set the months to be loaded in the process, reinforcing that is important to have the last 24 months in SMOG.

Loading frequency

     Once a month.

Reporting

Main queries

Roles & Access

List of application role + menu role  and explanation if we have several applications role with specials rules.

Authorization objects

List of authorization objects mandatory for the application.

5.2 Process Detail 

5.2.1.  Report/Process Definition 

This section represents the process with detail information for the application. Can include specific or special cases, complex logics , calculations, flows, among others.

6.0 Non-functional Descriptions 

6.1 Usability

Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system.  In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required.  Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.

6.2 Regulatory Compliance

Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region.  The software systems must be secure from unauthorized access.  The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.

6.3 Security

Security refers to essential aspects that assure a solution and its components will be protected against unauthorized access or malware attacks.  Important considerations related to security aspects of a system are User authentication, User authorization or User access privileges, data theft, malware attacks, data encryption, and maintaining audit trails, e.g., only Users with administrator access shall be able to create new accounts and assign data access privileges to the new accounts e.g.,

• All data will be encrypted in the dashboard
• Only authorised Users / Administrative Users will be able to access data.
• Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.

6.4 Performance

Performance defines how fast a software system or a particular section of it responds to certain User actions under a certain workload.  In most cases, this metric explains how long a User must wait before the target operation happens e.g., the page renders, a transaction is processed, etc., given the overall number of Users now.  Performance requirements may describe background processes invisible to Users, e.g., backup and speed of data transfers. 

6.5 Reliability

Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period.  Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period.  Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations.  The Maintenance Dashboard will display data from the previous refresh of data.   

6.6 Scalability

Scalability refers to the degree to which a solution can evolve to handle increased amounts of work.  The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts.  

6.7 Compatibility

Interoperability is the degree to which the solution is compatible with other components.  It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.

Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job.  To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).

6.8 Availability

Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).

6.9 Refresh of the Data

Frequency, data, and time of the data refresh in the data product.