Week 9

Summary of weekly
changes in SAP

29 November 2014

AM Incidents

AM Incidents - Overall Summary

No*. Type & INC No.

Area

Summary of Change

Users Impacted

BUs Impacted

INC0036958

Procureme
nt

Change of MRP Controller D08/S08 from user JBR024 to

JBU058.

Procurement users of DK

DK

INC700027572867

FI

GL Account 1931001 Added to FI Document Splitting

Category.

FI

DK02

INC000006733622

Users working with Purchase

requisitions.

Global

INC0038885

Procureme
nt

Updating Purchasing group Q24

Procurement users of QA.

QA

INC0030177

FI

MDG issue Bank Details in the validity period are not

unique when the Business partner has more than one
bank accounts

Finance users across all the

locations.

Global

INC0040291

FI

Maintain Funding currency USD in company code

GL01(Funding group assignment GJ37 Customizing)

Finance users in DK location.

DK

INC0039220

FI

Maintain Missing Currency conversions

Project Department users in UK

location.

UK

INC0041163

Procureme Change of MRP Controller D49/S49 from user IWK002 to

nt
MVA100

Procurement users of DK

DK

INC0025805

Procureme X1 price variance block not re determined when effective

nt
price is changed

Procurement users working with

material Purchase Orders

All

10

INC0019338

Procureme
nt

X1 price variance block is not triggered when PO is saved

using Save and Output option

Procurement users working with

material Purchase Orders

All

11

INC0026223

Procureme
nt

Item text on RFQ output

Procurement users working with

RFQs

All

#3

Procureme Updating of Custom fields for approver name and date in

nt
EBAN table

No*. Type & INC No.

Area

Summary of Change

Users Impacted

BUs Impacted

12

INC0014401

PMPS

DBU Onshore Time writing bug fix

DBU TW users

DK

13

INC0037736

Procureme
nt

Updating Purchasing group Q45/U45.

Procurement users of QA.

QA

14

INC700027689520

Maintenanc
e

Field Sub-Order made Input in Work Order Component

screen

Maintenance users

DK, GB

15

INC000006519890

PMPS

Added Wild Card search functionality for FLOC input field in

ZPM_PM_MASTERDATA REPORT

Maintenance Users

QA

16

INC0033928

PMPS

Code fix for setting HOLD status on WO

Maintenance Users

DK

17

INC0039431

R&A

Invisible the T codes in Process Roles from Employee Job

Role.

Employee Users

Global

18

INC0039177

R&A

Deleting few identified unwanted Job Roles

No User Impact

NA

19

INC0033895

BI

For include Error stack DTP in the process chain:

ZPC_FI_OPT_2

BI Reporting users

Global

20

INC0014208

BI

Tracking of spacing issues - submitted csv file have spacing

Qlik view Users

Global

21

INC0012132

R&A

Changes done in material contract viewer role

Procurement

Global

22

INC700027763031

FI

Old equity shares reported on cash call report for NO01 &
Change of logic in deriving value date in the cash call
statement

Finance users in Norway location

Norway

#4

No*. Type & INC No.

Area

Summary of Change

Users Impacted

BUs Impacted

23

INC700027629796

FI

PCO (Parent Company Overhead) on credit cost(Negative

Balance)- WBS is not calculated in SAP

Finance users in Norway location

Norway

24

INC0030933

FI

Translation ratio maintained for exchange rate type ZAO

Users in Angola

Angola

25

INC0032747

LO

Radioactive Data on Vessel Routing plan

Logistics users working with Vessel

routing plan

DK,QA

#5

1. Change of MRP Controller D08/S08 from user

Type : Incident

JBR024 to JBU058

Inc./CR No.: INC0036958

Functional Area : Procurement

BUs Impacted : DK

Who has been

impacted?

1. The procurement users of DK.

What was the issue/existing business

scenario?

What has changed/How has the issue

been resolved?

Requirement to change the MRP

controller D08/S08 from user JBR024
to JBU058.

MRP controller D08/S08 is now

assigned to user JBU058.

Support documents

1.

NA

What is the impact on end users?

The procurement users can now
use this new MRP

controller

2. GL Account 1931001 Added to FI Document

Splitting Category.

Type : Incident
Inc./CR No.: INC700027572867
Functional Area : FI

BUs Impacted : DK02

Who has been

impacted?

1. FI Business Users were not able to post to GL Accounts 1931001 in company code DK02

What was the issue/existing business

scenario?
Business requested to perform the required
checks and configurations before GL Account
1931001 is extended to company code DK02 in
OPZ.

Support documents

#7

What has changed/How has the issue

been resolved?
GL Account 1931001 is added in FI
Document Split Category.

What is the impact on end users?

It will allow business to post
the transactions to the GL
Account 1931001 in company
code DK02.

3. Updating of Custom fields for approver

name and date in EBAN table

Type : Problem Incident

Inc./CR No:INC000006733622
Functional Area :Global

BUs Impacted :Global

Who has been

impacted?

1. Users working with Purchase requisitions.

What was the issue/existing business

scenario?

Z fields in EBAN tables where not

getting cleared when release is revoked
for the PR

Support documents

NA

What has changed/How has the issue

been resolved?

What is the impact on end users?

Code fix is done to ensure that

the fields are cleared when the
release is revoked and updated
when the PR is released.

End users looking for PRs based

on the approver ID and release
dates will see the correct data
for all PRs changed henceforth.

4. Updating Purchasing group Q24.

Type : Incident.
Inc./CR No.: INC0038885
Functional Area : Procurement

BUs Impacted : QA

Who has been

impacted?

1. Procurement users of QA.

What was the issue/existing business

scenario?

Purchasing group Q45/U45 has

been updated as requested.

User service request for updating the

purchasing group Q24 for QA.

Support documents

#9

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

Updated purchasing group Q24
will be available for QA
procurement users.

5. MDG issue Bank Details in the validity period

are not unique when the Business partner has
more than one bank accounts
Who has been
impacted?

In MDG, if the Business partner or

vendor has more than one Bank details
If we try to delete the other Bank
details and change to new Partner
Bank category for same bank account
system gives an error Bank Details in
the validity period are not unique".

#10

Inc./CR No.: INC0030177

Functional Area : Finance/MDG

BUs Impacted : Global

1. Finance users across all the locations.

What was the issue/existing business

scenario?

Support documents

Type : Incident.

1.

NA

What has changed/How has the issue

been resolved?
We have reached out to SAP and
SAP provided an OSS Note
(1974330 - MDG check with API
memory) for the fix and the issue is
resolved by implementing the OSS
Note (1974330 - MDG check with
API memory) and got confirmation
from Business

What is the impact on end users?

End users can delete the other
partner bank category and change
to new partner bank category if
the Business partner or vendor
has more than one bank accounts
in MDGS tool

6. Maintain Funding currency USD in company

code GL01(Funding group assignment GJ37
Customizing)
Who has been
impacted?

1.

What has changed/How has the issue

been resolved?
In customization (Funding group
assignment), we have not
maintained our Funding currency
USD for GL01 company code hence
system unable to derive the Bank
account details in the customer
invoice layout. we have maintained
the necessary configuration change
and now system can derive the
bank details in customer invoice
layout.

Business posted a customer invoice

with USD currency in GL01 Company
code and generated the customer
invoice layout and found that Bank
details are not populating in the
customer invoice layout.

#11

Inc./CR No.: INC0040291

Functional Area : Finance

BUs Impacted : Denmark

1. Finance users in DK location.

What was the issue/existing business

scenario?

Support documents

Type : Incident.

NA

What is the impact on end users?

End users can send the invoices to
customers with correct invoice
layout.

7. Maintain Missing Currency conversions

Type : Incident.
Inc./CR No.: INC0039220
Functional Area : Finance

BUs Impacted : UK

Who has been

impacted?

1. Project Department users in UK location.

What was the issue/existing business

scenario?

We have checked with COE for the

missing Translation Ratios(Missing
currency conversion) in the system
and maintained the missing
translation ratios in the OBBS
transaction and got the UAT
successfully.

When the batch job

ZDS_PS_NWPLANCOST_UPD runs in
SAP for updating the currency ,
Business found that the currency
conversions(GBP-EUR and EUR-GBP
missing for Exchange rate type P)

Support documents

#12

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

End users can maintain the
exchange rate in OB08
transaction for the missing
currency conversions
successfully.

8. Changing MRP Controller D49/S49.

Type : Problem Incident

Inc./CR No: INC0041163
Functional Area : Procurement

BUs Impacted : DK

Who has been

impacted?

1. The procurement users of DK.

What was the issue/existing business

scenario?
Requirement to change the MRP
Controller D49/S49 from Ivan W.
Knudsen (IWK002) to Martin V.
Andersen (MVA100).

Support documents

NA

What has changed/How has the issue

been resolved?

What is the impact on end users?

MRP Controller D49/S49 has been

changed to Martin V. Andersen.

Changed MRP Controller will be

available in production system.

9. X1 price variance block not re determined

when effective price is changed

Type : Problem Incident

Inc./CR No: INC0025805
Functional Area : Procurement

BUs Impacted : All

Who has been

impacted?

1. Procurement users working with material Purchase Orders.

What was the issue/existing business

scenario?

What has changed/How has the issue

been resolved?

In case we have PO net price as same as

PR net price and X1 is triggered due to
some conditions added on the
PO(freight, documentation charges etc.).
If the condition is deleted or changed so
that we dont have any variance
between PR and PO price, X1 block is not
removed from the PO.
This issue occurred since the release
strategy was not re determined

Code changes are done to ensure

that X1 price variance will be
removed when there is no price
variance on the PO

Support documents

NA

What is the impact on end users?

X1 block will automatically be
removed from the PO, when
there is no variance.
The users will not be required
to manually change the PO to
remove the block.

10. X1 price variance block is not triggered

when PO is saved using Save and Output
option
Who has been
impacted?

Type : Problem Incident

Inc./CR No: INC0019338
Functional Area : Procurement

BUs Impacted : All

1. Procurement users working with material Purchase Orders.

What was the issue/existing business

scenario?

What has changed/How has the issue

been resolved?

What is the impact on end users?

When users save the PO using Save and

Output(Control + P) option, X1 block is
not triggered on the PO even when we
have price variance.

Code changes are done to ensure

that X1 block is triggered when
PO is saved with Save and
Output option

X1 block will be triggered

correctly on all Purchase
Orders
where
variance
conditions are satisfied.

Support documents

NA

11. Item text on RFQ output

Type : Problem Incident

Inc./CR No: INC0026223
Functional Area : Procurement

BUs Impacted : All

Who has been

impacted?

1. Procurement users working with RFQs

What was the issue/existing business

scenario?

What has changed/How has the issue

been resolved?

Item text on the RFQ output is not

updated with the updated text on the
output. It is picked from the material
master Basic data text.
Currently buyers cannot modify the text
if any requirement arises.

Code changes are done so that

the system will pick the text
updated on the RFQ.

Support documents

NA

What is the impact on end users?

Item text which is updated on
the RFQ will be sent to the
Vendor.
In case no changes are done on
the text, no change in
functionality will be observed.

12. DBU Onshore TW Bug fix

Type : Incident
Inc./CR No.: INC0014401
Functional Area : PMPS

BUs Impacted : DK

Who has been

impacted?

1. DBU Onshore TW Users

What was the issue/existing business

scenario?
While time writing, correct price
determination was not happening
which is maintained in KP26. Also,
when the work order was changed in
the same line, re-determination of
Sender cost center and Activity type
does not happen.

Support documents

#17

What has changed/How has the issue

been resolved?
Code changes were done where
price determination is correctly
done and when work order is
changed on the same line, correct
Sender Cost Center and Activity
type is maintained.

What is the impact on end users?

After this change, correct Price
will be posted to the correct
cost centers and Activity type
which is maintained in KP26.

13. Updating Purchasing group Q45/U45.

Type : Incident.
Inc./CR No.: INC0037736
Functional Area : Procurement

BUs Impacted : QA

Who has been

impacted?

1. Procurement users of QA.

What was the issue/existing business

scenario?

Purchasing group Q45/U45 has

been updated as requested.

User service request for updating the

purchasing group Q45/U45 for QA.

Support documents

#18

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

Updated purchasing group
Q45/U45 will be available for QA
procurement users.

14. Field Sub-Order made Input field in Work

Order Component Screen

Type : Incident.
Inc./CR No.: INC700027689520
Functional Area : Maintenance

BUs Impacted : DK, GB

Who has been

impacted?

1. Maintenance users of DK and GB.

What was the issue/existing business

scenario?

Screen variant for Work Order

Component screen updated in
order to make field Sub-Order as
Input field.
The field is now available for input.

Due to a previous CR change of Work

Order Component screen layout
modification, the field Sub-Order in
the Component screen was made as
display only field.
The users from DBU required this field
to be available for Input in order to
enter recipient for whom the material
or service is destined.

Support documents

#19

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

Users will now be able to use the
field Sub-Order to enter recipient
for whom material/service is
destined whenever required.

15. Added Wild Card search functionality for FLOC

input field in ZPM_PM_MASTERDATA REPORT

Type : Incident
Inc./CR No.: INC000006519890
Functional Area : Maintenance

BUs Impacted : QA

Who has been

impacted?

1. QA Maintenance users.

What was the issue/existing business

scenario?

Enhanced the report functionality

by addition of Wild Card search for
Functional Location.

There was a requirement from

business to enhance report
functionality so that Wild Card search
functionality is possible for Functional
Location input field of
ZPM_MASTERDATA report.

Support documents

#20

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

After this change, Maintenance
users can search Functional
Location based on any part of
string in ZPM_MASTERDATA
report.

16. Code fix for setting HOLD status on WO

Type : Incident
Inc./CR No.: INC0033928
Functional Area : Maintenance

BUs Impacted : DK

Who has been

impacted?

1. DK Maintenance users.

What was the issue/existing business

scenario?

Code fix has been implemented so

that HOLD status will be set in the
released work order if operation is
deleted.

The users were facing an issue in

setting HOLD user status for GE01 &
CS02 work orders if operation of work
order is deleted.
In such a cases, setting HOLD status
was not possible.

Support documents

#21

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

After this change, Maintenance
users will be able to save the
WO (GE01 & CS02) even after
changes happened in the
operations for release WO at
HOLD user status is set.

17. Invisible the T codes in Process Roles from

Employee Job Role.

Type : Incident
Inc./CR No.: INC0033928
Functional Area : R&A

BUs Impacted : Global

Who has been

impacted?

1. Employee Type Users.

What was the issue/existing business

scenario?

What has changed/How has the issue

been resolved?

Few of the T codes in the Process Roles

are visible from Employee Job Role.
Because of that MDGS screen fields got
changed.

Made the required T codes

Invisible in the Menu of the Process
Roles from the Job Role: Employee.

Support documents

#22

1.

NA

What is the impact on end users?

MDGS screen is going to be
normal for the users in NWBC.
There will be no impact from
the access point of view.

18. Deleting few identified unwanted Job Roles

Type : Incident
Inc./CR No.: INC0039177
Functional Area : R&A

BUs Impacted : NA

Who has been

impacted?

1. No User Impact.

What was the issue/existing business

scenario?

Deletion TR has been created for

the list of Roles.

Identified few unwanted Job Roles in

OPZ to be deleted.

Support documents

#23

1.

What has changed/How has the issue

been resolved?

What is the impact on end users?

Below list of Job Roles will not
be available in OPZ:

NA

ZC:XXXXXXXX:FI-OT_WF_VIM_SUPP
ZC_GBXXXX_FI_PERIOD_END_ACCO
ZC_GL01XXX_FI_PERIOD_END_ACCO
ZC_KY01XXX_FI_PERIOD_END_ACCO
ZC_KY02XXX_FI_PERIOD_END_ACCO
ZC_KZ01XXX_FI_PERIOD_END_ACCO
ZC_MX01XXX_FI_PERIOD_END_ACCO
ZC_NO01XXX_FI_PERIOD_END_ACCO
ZC_QA01XXX_FI_PERIOD_END_ACCO
ZC_QA02XXX_FI_PERIOD_END_ACCO

19. For include Error stack DTP in the process

Type : Incident

chain: ZPC_FI_OPT_2

Inc./CR No.: INC0033895

Functional Area : BI

BUs Impacted : Global

Who has been

impacted?

1. FIJV reporting for FIJV daily chain

What was the issue/existing business

scenario?

Added the Error DTP step in

process chain.

Identified error DTP was not running

automatically as part of the process
chain

Support documents

#24

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

Process chain will function
better with this change with
few occurrences of Failure

20. Tracking of spacing issues - submitted csv

file have spacing

Type : Incident
Inc./CRNo.:INC0014208
Functional Area : BI

BUs Impacted : Global

Who has been

impacted?

1. Qlikview users who provide MD flat files on SharePoint.

What was the issue/existing business

scenario?

What has changed/How has the issue

been resolved?

What is the impact on end users?

Code changed for transformation

to ZMD_O11 and ZMD_O25 DSOs.

1. Problem with few fields with spacing in the file

extracted by qlikview, code was written in BI to
enable the spaces and special characters

Support documents

#25

1.

NA

Qlikview Users will be able to read the

text with proper spacing

21. Changes done in the material contract

Type : Incident

viewer role for display of global contracts

Inc./CRNo.: INC0012132
Functional Area : R&A

BUs Impacted : Global

Who has been

impacted?

1. Procurement Users using Global Contracts

What was the issue/existing business

scenario?

We have changed the value of

Purchasing group as * for the
Contract Viewer
role(ZD:XX:XXXX:PRMM_MATCONTVIEWER where
XXXX= GBXX, DK01, US01 etc.)

The users from all the locations were

not able to view global contracts, since
there was a check on the purchasing
group

Support documents

#26

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

They will be able to view the

global contracts

22. Old equity shares reported on cash call report

for NO01 & Change of logic in deriving value date
in the cash call statement
Who has been
impacted?

What has changed/How has the issue

been resolved?

After having equity adjustments in the

ventures, when execute cash call
statements, old equity shares also
visible in the report with value 0.

Added the condition in the

program zfi_jv_cashcall for the
issue old equity shares reported
on cash call report.

Presently value date is showing in the

cash call statement 14 days from the
invoice date and business wants to
change this to 15 days

Changed the days in the program

zfi_jv_cashcall to derive the
value date as 15 days from the
invoice date as business required.

#27

Inc./CR No.: INC700027763031

Functional Area : Finance
BUs Impacted : Norway

1. Finance users in Norway location.

What was the issue/existing business

scenario?

Support documents

Type : Incident

1.

NA

What is the impact on end users?

After required changes, Cash
Call Statement will work as
expected.

23. PCO (Parent Company Overhead) on credit

cost(Negative Balance)- WBS is not calculated in
SAP
Who has been
impacted?

1.

What has changed/How has the issue

been resolved?
Created negative threshold in
stepped rate rule
Because of maintaining negative
threshold causing another issue
that the output for Total
Overhead Allowed and Total
Overhead Calculated for Previous
Periods" is incorrect. For this,
implemented OSS Note 1622186
and issue has been resolved.

Presently system able to calculate PCO

on debit cost(positive balance) in WBS
and at the same time unable to
calculate PCO on credit cost(negative
balance).

#28

Inc./CR No.: INC700027629796

Functional Area : Finance
BUs Impacted : Norway

1. Finance users in Norway location.

What was the issue/existing business

scenario?

Support documents

Type : Incident

NA

What is the impact on end users?

Now system will be able to
calculate Parent Company
Overhead on credit
cost(negative balance) on WBS
in SAP.

24. Translation ratio maintained for exchange rate

type ZAO USD-AOA from 2010

Type : Incident

Inc./CR No.: INC0030933

Functional Area : All
BUs Impacted : Angola

Who has been

impacted?

1. Users in Angola

What was the issue/existing business

scenario?

Translation ratio maintained for

ZAO exchange rate type for USDAOA from 2010.

Users unable to change old contracts

since translation ratio maintained from
2012.

Support documents

#29

1.

What has changed/How has the issue

been resolved?

NA

What is the impact on end users?

Users should be able to
maintain exchange rate with
type ZAO from 2010 onwards
so that they can change old
documents as well.

25. Radioactive Data on Vessel Routing plan

Type : Incident

Inc./CR No.: INC0032747

Functional Area : Logistics
BUs Impacted : DK,QA

Who has been

impacted?

1. Logistics users working with Vessel Routing plan

What was the issue/existing business

scenario?

Code changes are done to ensure

that the radioactive data is always
printed for radioactive materials
and printed only for radioactive
materials.

Sometimes Radioactive data is not

printed on the routing plan for
radioactive materials.
In some cases, radioactive data is
printed for materials that are not
radioactive

Support documents

#30

What has changed/How has the issue

been resolved?

1.

NA

What is the impact on end users?

Users will now see the correct
radioactive data on the routing
plan.

AD CRs

31

AD CRs - Overall Summary

No*.

Type & CR No.

Area

Summary of Change

Users Impacted

BUs Impacted

CR 2142

PM

Work Order and Notification Priorities descriptions

changed

200+

DK, GB, QA, KZ

CR 2371

PS

50-200

DK & GB

CR 1747

FI

Vendor Maintenance authorization updates in ECC - Part I

20-50

All

CR 2281

FI

VD02 and VD03 to be added to the Finance Local APAR

Master Data Maintainer role

20-50

All

CR 2273

FI

T-Code ME2DP to be added to 'Invoice Processor' role and

removed from 'Payment Processor' role

20-50

All

CR 2173

FI

Create new global roles 'Finance Inquirer' and 'Finance

Approver'

20-50

All

CR 1994

FI

Post the unplanned depreciation independently and

posted in the month of X should have no impact on
planned DD&A until month X+1

20-50

GB

CR 2247 & 2166

CPL

New enhancement in ZMM_REQUIS

20-50

All

CR - 2197

CPL

Kits with Dangerous Goods handling in Logistics

20-50

All

10

CR - 2426

CPL

MAP update with Subcontracting (refurbishment with

changed material number)

20-50

All

11

CR 1926

BI

20-50

DK-EBJ/Qatar

#32

New job role for AFE Master Data Maintenance

Removing Filter on Billable Recovery Indicators from

Master Data in BI-Cash Call Reports JV-11/12 (1/4)

1. Work Order and Notification Priority

description change

Type : CR
Inc./CR No.: 2142
Functional Area : Maintenance
BUs Impacted : DK, GB, QA & KZ

Who has been

impacted?

Maintenance users

What was the issue/existing business

scneario?
There is a set of priorities available as
per Maersk Prioritization Matrix to
record the priority of Maintenance task
in Work Order and Notification. Based
on this, the dates are calculated.
Business requirement is to update the
descriptions for these priorities in order
to give more meaningful descriptions
while Notification and Work Order
scheduling.

Support documents

#33

CR - 2142

What will change/what is the solution?

Customizing change implemented
to update Priority Descriptions in
Work Order and Notification as per
business requirement.

What is the impact on end users?

Users will now get a more
meaningful and descriptive Priority
list in Work Order and Notification.

2. Create a job role AFE Master Data Maintainer

Type : CR
Inc./CR No.: 2371

Functional Area : Project Systems

BUs Impacted : DK & GB
Who has been
impacted?

Project Systems Master Data Maintenance users

What was the issue/existing business

scneario?
Currently the transactions for AFE
Master Data Maintenance are under the
role for Finance Local GL/JV Master Data
Maintenance.
Anyone requiring AFE Master Data
Maintenance would have to hold the FI
Local GL/JV master data maintenance
role which is a very powerful role and
not required for AFE Master Data
Maintenance.

Support documents

#34

CR - 2371

What will change/what is the solution?

New job role for AFE Master Data
Maintenance activity has been
created.
This new role is to be assigned to
required users in Feb 14th release
and in Feb 28th release, the
Finance role is to be removed from
same users.

What is the impact on end users?

Meaningful segregation of roles.
Users requiring AFE MDM can
continue to do so using the new
role without holding the powerful
Finance role.

3. Vendor Maintenance authorization updates in

ECC - Part I

Type : CR
Inc./CR No.: 1747
Functional Area : FI

BUs Impacted : Global

Who has been

impacted?

1. Local vendor master maintainer role users

What was the issue/existing business

scenario?
Due to Compliance issue few
transactions codes from Global vendor
master maintainer and Local vendor
master maintainer need to be
removed.

Support documents

#35

What has changed/How has the issue

been resolved?
T codes: FK08,FK09,XK01 and
S_ALR_87012090 are removed
from the Process Role: Global
vendor master maintainer .
T codes: FK01, FK05, MK01, Mk02
and S_ALR_87012090 are
removed from the Process Role:
Local vendor master maintainer

UAT mail from RHO04, Josang, Kathrine and Helle Dyrting

TR document link has updated in the RFC tool and RFC Link # CR #1747

What is the impact on end users?

Users are not going to have the
below T codes from the
Process Roles:
T codes: FK08,FK09,XK01 and
S_ALR_87012090 from the
Process Role: Global vendor
master maintainer .
T codes: FK01, FK05, MK01,
Mk02 and S_ALR_87012090
the Process Role: Local vendor
master maintainer.

4. VD02 and VD03 to be added to the Finance

Local APAR Master Data Maintainer role

Type : CR
Inc./CR No.: 2281
Functional Area : FI

BUs Impacted : Global

Who has been

impacted?

1. Local vendor master maintainer users.

What was the issue/existing business

scenario?
Local Vendor Master Data Maintainers
need access to transaction codes VD02
and VD03 in order to update the sales
area on customers.

Support documents

#36

What has changed/How has the issue

been resolved?

T codes: VD02 & VD03 are

assigned to Process Role: Local
vendor master maintainer.

What is the impact on end users?

Local Vendor Master
Maintainers are able to update
and view the sales area on
customers.

UAT mail from RHO043, kjo034 and RLK006

TR document and BPD has updated in the RFC tool and RFC Link # CR # 2281

5. T-Code ME2DP to be added to 'Invoice

Processor' role and removed from 'Payment
Processor' role
Who has been
impacted?

What has changed/How has the issue

been resolved?

Access to t-code ME2DP to request

milestone payments should be
changed as follows:

T code: ME2DP is removed from

AP Payment Processor and
assigned to AP Invoice Processor.

Added to "AP Invoice Processor" role.

Removed from "AP Payment
Processor" role

#37

Inc./CR No.: 2273

Functional Area : FI

BUs Impacted : Global

1. AP Payment Processor and AP Invoice Processor users.

What was the issue/existing business

scenario?

Support documents

Type : CR

What is the impact on end users?

AP Invoice Processor can able
to post the down payment
request.
AP Payment Processor will not
be able to access the same
transaction.

UAT mail from Patel, Yogesh and Houston, Robert

TR document and BPD Link has updated in the RFC tool and RFC Link # CR # 2273

6. Create new global roles 'Finance Inquirer' and

'Finance Approver'

Type : CR
Inc./CR No.: 2173
Functional Area : FI

BUs Impacted : Global

Who has been

impacted?

1. 'Finance Inquirer' and 'Finance Approver users.

What was the issue/existing business

scenario?
Create new Job Roles: 'Finance
Inquirer' and 'Finance Approver.
Due to resolving the compliance, these
Job Roles are requested to be created.

Support documents

#38

What has changed/How has the issue

been resolved?

What is the impact on end users?

'Finance Inquirer' comprising with

the following process roles:
Accounts Payable Inquirer
A /P Master Data Inquirer
Accounts Receivable Inquirer
A/R Master Data Inquirer
FA Reporter and GL Inquirer
JV Accounting Master Data display
JV Financial Reporter
Management Reporter
'Finance Approver' comprising the
following process roles:
Budget Approver
Project Approver

UAT mail from BBH018, Ringrose, Kevin and YPA009

TR document has updated in the RFC tool and RFC Link # CR #2173

New Job Roles: Finance

Inquirer and Finance
Approver will be available to
the users.

7. Post the unplanned depreciation independently and

posted in the month of X should have no impact on
planned DD&A until month X+1
Who has been
impacted?

CR was raised to post the Post the

unplanned
depreciation
independently and posted in the
month of X should have no
impact on planned DD&A until
month X+1

#39

Inc./CR No.: 1994

Functional Area : FI

BUs Impacted : GB

GB finance users.

What was the issue/existing business

scenario?

Support documents

Type : CR

What has changed/How has the issue

been resolved?

What is the impact on end users?

Created new transaction type

groups and new transaction types
in the chart of depreciation GB00 .

Waiting for UAT confirmation from McIntosh, Rachael

Configuration rational has updated in the RFC tool and RFC Link # CR #1994

Users can able post the

unplanned depreciation
independently and posted
in the month of X will
have no impact on
planned DD&A until
month X+1

8. New enhancement in ZMM_REQUIS

Type : CR
Inc./CR No.: 2247 and 2166
Functional Area : CPL

BUs Impacted : Global

Who has been

impacted?

1. Users executing ZMM_REQUIS

What was the issue/existing business

scenario?
In ZMM_REQUIS there is no
column to show requisition
approval date and workflow
holder.

Support documents

#40

What has changed/How has the issue

been resolved?
Added new columns DOA Approval
Data and Requisition workflow
holder to display requisition
approval date and User ID showing
workflow holder

RFC Link # CR #2247

What is the impact on end users?

With the new enhancement in
ZMM_REQUIS users will be
able to know more data for
requisitions

9. Kits with Dangerous Goods handling in

Type : CR
Inc./CR No.: 2197

Logistics

Functional Area : CPL

BUs Impacted : Global

Who has been

impacted?

1. Logistic users

What was the issue/existing business

scenario?
In system there is no scenario to
inform the receipt of dangerous kit
materials

Support documents

#41

What has changed/How has the issue

been resolved?
Created new DG profile indicator
Z02 which can be maintained for
Dangerous kit handled materials in
material master
When the specific DG profile
indicator material is received in
WH, a new information screen
shows in MIGO transaction
informing Handel DG kit
materials

RFC Link # CR #2197

What is the impact on end users?

New enhancement will be
helpful for users in identifying
the materials which are needs
to be handled as a kits in
warehouse.

10. MAP update with Subcontracting

(refurbishment with changed material

number)
Who has been
impacted?

Support documents

#42

Inc./CR No.: 2426

Functional Area : CPL

BUs Impacted : Global

1. Logistic users

What was the issue/existing business

scenario?
Enhancement E62 is not able to
execute for the subcontracting
Refurbishment with changed
material number scenario.

Type : CR

What has changed/How has the issue

been resolved?

What is the impact on end users?

Code fix is made the

subcontracting Refurbishment
with changed material number
scenarios by which system is able
to execute E62 enhancement and
maintain MAP price

The MAP price is plant will be

maintained in plant for the
refurbishment stock for
subcontracting
Refurbishment with changed
material number

RFC Link # CR #2426

11. Remove Filter on Billable Recovery Indicators

from Master Data in BI-Cash Call Reports JV-11/12

Type : CR
Inc./CR No.: CR 1926

Functional Area : Finance

BUs Impacted : All

Who has been

impacted?

All Business Units , who uses this FI-JV report

What was the issue/existing business

scenario?
The current BI Cash Call Reports JV-11/12
is based on Open Invoice Items both from
SAP and Open Text which are Billable to
the Partners.
Billable items are derived from the
Recovery Indicator (RI) maintained in the
Master Data of the relevant Cost Object
(Cost Center, WBS etc.)
The configuration in SAP allows for the
Recovery Indicator to manually
overwritten during Posting.
Add an additional column for document
type in JV-12 report

Support documents

What is the impact on end users?

The business from Qatar & Esbjerg

would like the filter on Billable items
based on Master Data Recovery
Indicator to be removed from both
JV-11 & 12.

The Cash Call Report will now show all

items from Open Invoices made to
the Balance sheet Account, including
those which arent billable to the
Partners

In its place, a Selection Variable on

Recovery Indicator from Master Data
is to be included

The impact of this would be especially

felt by DK-Esbjerg who are the main
users of this report so far.

JV-12 should include an additional

column showing RI from Master Data

Users must be aware to select the

correct Recovery Indicator

JV-12 should include an additional

column showing Document Type

Users will able to see document type

in JV-12 report

CR Link: http://team.apmoller.net/sites/MouseRFC/_layouts/listform.aspx?PageType=4&ListId={385A6DBB-B4DF-4FCF-956B804AEF22567B}&ID=1926&ContentTypeID=0x010027C8F37DCC005349ADEC651B2884F4F6 D Lin

FD Link:

#43

What will change/what is the solution?

http://sfrmappp104:08010/sap/bc/solman/SolmanDocuments/001?_CLASS=SOLARGEN&_LOIO=0017A47720241ED292BB20356CF903DE&LANGUAGE=EN&RELEASE=620&IWB_INDUSTRY=/KWCUST/&TMP_IWB_TRY_OTHER_LANG=X&TMP_IWB_TRY_OTHER_IND=X&TMP_IWB_TASK=PREVIEW2&

Project CRs

44

Project CRs - Overall Summary

No*.

Type & CR No.

Area

Summary of Change

Users Impacted

BUs Impacted

CR 2302

FI

Configuration for exchange rates to configure USDA to

zero.

Finance

Angola

CR 2330

FI

Changes to UK Closing Cockpit

GB

CR 2314

FICO, AA,
JVA & CPL

Implement Maersk Colombia in DK08

All the users of new DK08 Company

Code

DK

#45

1. Configuration for exchange rates to

configure USDA to zero.

Type : Project CR
Inc./CR No.: 2302
Functional Area : Finance

BUs Impacted : Angola

Who has been

impacted?

Finance

What was the issue/existing business

scenario?

Configuration of ratios and USDA

exchange rates for rate type M
and ZM in order for local currency
3 to be near zero for new
postings.

Due to changes made to currency

setup in Angola, third currency
USDA should be ignored. Because
we cannot disabled 3rd currency,
we ignore it by maintaining it in
order to be near to zero.

Support documents

What has changed/How has the issue

been resolved?

CR - 2302

What is the impact on end users?

No impact for user daily tasks.

2. Changes to UK Closing Cockpit

Type : CR
Inc./CR No.: 2330

Functional Area : Project/ FI

BUs Impacted : GB
Who has been
impacted?

GB Location: Changes to UK Closing Cockpit

What was the issue/existing business

scneario?
The Closing cockpit Template has to be
updated to accommodate the new task
and to get rid of some non relevant task.
The user responsible and task processor
has been updated as per the existing
users.

What will change/what is the solution?

There are some new period end
task has been added
Some existing period end task has
been removed from the template.
Task processor and task
responsible user update.

What is the impact on end users?

There are some new period end
task has been added.
Some existing period end task has
been removed from the template.
Task processor and task
responsible user update.
Robust Period end exhaustive task
list
Better User Responsibility and
assignment.
Template alignment as per the
exsting Period end process
requirement.

Support documents

CR - 2371
RFC Document has been Updated with : Config rational, BPD and UAT Signoff.

#47

3.Implementing Maersk Colombia in DK08

Company Code

Type : CR
CR No.: 2314
Functional Area : FICO, AA, JVA & CPL
BUs Impacted : DK

Who has been

impacted?

All the users of new DK08 Company Code

What was the issue/existing business

scneario?
There is a legal requirement to roll out
one new company code in SAP for
implementing Maersk Colombia. This
company code (DK08) is a non-operated
Joint Venture

Support documents

#48

CR - 2314

What will change/what is the solution?

SAP team has worked with business
owner of the new DK08 company
code to identify the business
requirements of the new company
codes and after business sign off,
SAP project team has proceeded
with building, testing, & deploying
the new company code on SAP. No
RICEFs were involved, just
configuration with no impact on
any other OUs.

What is the impact on end users?

New legal entities would come into
existence. It would be required to
record the day to day business
transactions from book keeping
perspective. It is also required to
follow the reporting principles in
line with other DKXX company
codes.