Change Request | SAP Next | Merck Group

Titl
ID ZCBX_LOG report results enhancement
e

A1 | Request details

Validated Stream/Function: Order to Cash (O2C) - SD

OR
Non-Validated Stream/
Choose One:
Function:

Other Involved SAP

Add other involved SAP modules here
modules:

Type of release: Independent

Requester: Raquel Diaz / Tiziana Gallo

Sponsor: Jean Chabbert/ Nathalie Cousin

Emergency: YES or NO? If Yes, proceed to section A1.1: NO

A1.1 | Emergency Justification (If applicable)

Type: Legal requirement Business opportunity ● Risk of business loss

Please provide justification for emergency.

Impact if moving with a planned release /

Why not with a planned release?
Please state details and deadlines about potential
local law involvement
Effort estimation of impact in €:

Possible workaround:

Effort estimation of workaround in €:

Target date for move to quality?
Target date for move to production?

Page 1 V3.0

Titl
ID ZCBX_LOG report results enhancement
e
A2 | Business case
Provide a clear, precise description of the
current situation.
Provide a clear, precise description of the
requested new or changed functional or process
(non-technical / business view):
Provide a detailed explanation of expected
benefits:
Provide Quantified benefits (cost, resources) to
be saved per year. Statements on process
optimization, compliance to regulatory
requirements, human error reduction, etc. are
acceptable
If this is a support enhancement, is there an
impact to Recharged or the global template? If
yes, explain impact.
Page 2
Change Request | SAP Next | Merck Group
 Currently, ZCBX_LOG transaction to monitor failed
ZCBX and ZCBY outputs is manually run by BPEX
team every day to track failures for P2 and W2
countries.
The list of results of this report is providing failed
outputs for all sales organizations and it is not
possible to differentiate and filter results by country
or any other header value
 This report takes too long to be run and provide the
results therefore users waste too much time waiting
for it to be ready
For previous points, we request the following changes:
 Once the report is run, to get additional columns on
the results lists to indicate header fields: Sales
organization, sales group, sales office, sold to party,
document date, created by, net value
 Create a batchjob that runs the report automatically
and sends the results by e-mail to the indicated
teams
 Moving to W3 and W4 Go-live, new countries out of
WEU and out of BPEX team scope will be in PRP and
will have to monitor the failed Crossbox orders using
the ZCBX_LOG transaction.
Possibility to filter results by country is a need to
allow every country/area to keep track of their
failed orders, and take action to solve the root cause
and release shipments to customers.
 Getting additional header fields on the results list
will facilitate the use of the report to follow up by
customer, merck employee, etc
 Having batchjob to run report automatically and
sending results by e-mail, will save time to the
monitoring teams and this time will be used to work
on the trouble shooting to release these orders.
ZCBX_LOG report being currently run for P2 and W2
countries gives already thousands of failed lines on the
results list which consumes the user endless time in effort in
running the report and extrapolating the lines per sales org
and or sites. As more countries going live will increase the
number of results, thus causing the report to time out and
causes delays in clearing the queue.
If these changes are not implemented before July, the
monitoring team in every country/area will not be able to
track failures.
This change will impact all countries running this report and
benefit will be applicable to all of them
V3.0
 Change Request | SAP Next | Merck Group

Titl
ID ZCBX_LOG report results enhancement
e

A3 | Further information

Requirements related to this change request:

AFFECTED (but not changed/updated) requirement
IDs and URS # or folder path where they can be found.
CHANGED / NEW requirement URS ID #. If to be
created, provide expected ALM folder placement:

Any further aspects to be addressed:

- User Interface, reports, forms (design, layout,
purpose/scope)
- Data (migration, import/export, transformation,
storage, interface)
- Privileges (access and user permissions to
transaction and data)

Test case name from test case library (only when using
HP ALM) otherwise include test document name:
Is change a result of an Incident, defect or deviation: NO

If yes, provide ID#

Will training material be affected? YES

B1 | IT statement

IT SME – Name: IT team effort (hours):

Description of the expected technical
changes to be made and general
development responsibility statement:
Documents to be created/changed
(design/technical documentation etc.):
Complexity Choose the complexity

SAP system only:

Other involved/impacted Choose involved SAP Module
SAP Module/System

B2 | Transport details, regression relevance

Is Change Document
YES or NO? CD #(s)
(CDs) already created:
Details on ChaRM and transports:
The modification has potential impact on other SUB / Org. units
YES or NO?
(Regression):
If regression relevant ‘yes’, then
- Processes and functions to be tested:

Page 3 V3.0
 Change Request | SAP Next | Merck Group

Titl
ID ZCBX_LOG report results enhancement
e

- By which SUB(s) or org. unit(s):

C1 | Process Sub-Steam lead/Global Stream Lead statement

Lead Name: Team effort (kEUR):

Change Type: Choose Change Type Rationale: Choose Rational

Site/Country Impacted: Global Impact? YES or NO?

Is additional authorization required? YES or NO?

D1 | Authorization statement (input from SAP Security – GRC)

SAP Security Contact:

Impact on authorization business roles of the global
YES or NO? If ‘Yes’, please fill section D2
template?
Impact on authorization roles? YES or NO? If ‘Yes’, please fill section D3

D2 | Impact on authorization business roles of the global template

Technical authorization business role names:

Short description of business role:

Action Name of authorization role(s) to be added/changed/removed

Add
Change

Remove

Page 4 V3.0
 Change Request | SAP Next | Merck Group

Titl
ID ZCBX_LOG report results enhancement
e

D3 | Impact on authorization roles

Technical name of authorization role(s):

Short description of Authorization Role:

Documents to be created/updated defining the
Authorization Role
Add / Remove Authorization object Authorization field Field content / values

Include this authorization also into an application support role? YES or NO?

If ‘Yes’, please specify the role name:

Add this new authorization also into the migration role? YES or NO?

Add the new authorization only into a local authorization role? (e.g. Add-on-Role) YES or NO?

If ‘Yes’: comment / justification:

History of change (Remove upon save):

Version Changes compared to previous version

1.0 Initial version.

Section A1: Updated labels and added sub-stream processes
Section A1-1: added more information to capture for Emergency justification
2.0 Section A2: add field for impact to Recharged project
Section D1: added Data Privacy questions
Sections E1-E3: aligned with questions from Authorization template

Updated and split table values in Global Stream and Functionalities

3.0 Removed Data Privacy section
Updated description on A2 business case questions
Added more questions to A3 to consider other aspects for change

Page 5 V3.0