clarifications no. 2: rfp no. 2018-0092/jibril · 2018. 7. 26. · clarifications no.2: rfp no....

Clarifications No. 2: RFP No. 2018-0092/JIBRIL

Provision of SAP Services.

___________________________________________________________________________

Page 1 of 4 7/26/2018

Item

No.

Question

Answer

1 Please provide details of the SAP

installations. Does CTBTO have 3

systems landscape (Development, Test

and Production) for SAP environment?

There are three SAP applications

(ECC, SRM and Portal), and each has

3 installations (1: Development, 2:

Quality, 3: Production). In addition,

there is one sandbox system and a

disaster recovery landscape (for ECC,

SRM and Portal).

2 Please mention the SAP Products and

their Versions to be supported for this

engagement.

The current products and versions are

(but might be upgraded during service

delivery, see Service 2.5):

1. SAP ERP 6.0 EHP6

2. SAP SRM 7.0 EHP2

3. SAP 7.3 NetWeaver PORTAL

The database for all application is

Oracle Database 12c Enterprise Edition

release 12.2.0.1-64 bit

3 What are the SAP Functional modules

in the scope of this engagement other

than those mentioned in the RFP

document.

The current scope of SAP functional

modules is Materials Management,

Project Systems, Financial Accounting,

Controlling, Public Sector

Management (incl. Funds and Grants

Management), Payroll, Personnel

Management, Organizational

Management, Travel Management,

Workflow. Functional modules might

be enhanced during service delivery.

4 Please provide details of non-SAP

system interfaces with SAP modules in

the scope of this project and also

provide the middleware details.

The current interfaces (which might

change during service delivery) are:

1. Compass (Project management

software);

2. SAP Success Factor (E-recruitment

& Performance Appraisal);

3. Microsoft Active Directory Service;

4. Vienna International Center Security

system for sharing staffs' pictures;

5. UNIDO telephone bill exchange;

6. HR Reporting tool server; and

7. CTBTO Intranet portal server.

All of the above systems have been

integrated to exchange table data as file

system import/export via ftp/sftp file

transfer tool.

5 Do you require ''On Call'' offshore

support for this engagement? If Yes,

The support for service 2.3 "Remote

Support" is provided via the Jira



___________________________________________________________________________

Page 2 of 4 7/26/2018

please provide specific requirements. ticketing system. Telephone calls

might be arranged on an exceptional

basis.

6 Please share the SAP support ticket

trends for all the SAP modules per

Legal entity and geography for the last

2 years.

Please find on sheet “Statistics”,

attached to this clarifications, a trend of

closed tickets by functional area since

1 Jan 2017 (please note that CTBTO

has only one Legal Entity and one

Geography (i.e. Vienna)). A subset of

these tickets will be assigned to the

service 2.3 "Remote Support" of the

ToR.

7 Would this engagement involve multi-

Vendor management and governance?

Please elaborate and provide necessary

details.

The following main stakeholders will

be involved in SAP services: third

party vendor for hosting, CTBTO SAP

team, CTBTO business focal points

and users, Contractor(s) for current

RFP (CTBTO_RFP2018-0092-

JIBRIL).

8 Who will be responsible for SAP

BASIS and Security Support for this

engagement? Please elaborate and

provide specific details.

SAP Basis and Security Support is

performed by CTBTO and the hosting

partner.

9 Please Specify the FRICEW counts in

the existing landscape.

Current number of FRICEWs by

functional area: Finance: 48, Supply

Chain: 48, HR: 9, Travel: 6, (the

number might change before and

during the service).

10 Onsite key personnel requirement is

indicated as 600. Please let us know

whether the resources are expected to

work onsite continuously for the

indicated man-days? OR the onsite

resources are required to travel multiple

times to Austria? This will have impact

on multiple Visa charges and travel

costs.

The 600 days will be split on 3

resources (i.e. 200 days each). The

resources are expected to work onsite

continuously (with the exceptions of

CTBTO holidays, leave, trainings, sick

days etc.). Travel is only required at

service start and service end.

11 Ref 2.8 onsite travel (Page 15 of RFP):

Return trip costs include flight charges.

Will CTBTO pay other logistic

expenses like Accommodation, Food,

local conveyance and Perdiem to the

Call-off resources?

CTBTO will pay the return trip and a

lump sum DSA (i.e. Daily Subsistence

Allowance) per onsite day. Please

include all relevant expenses in your

trip or lump sum proposal as per the

Format of the Financial Proposal.

12 Will CTBTO pay the Visa Charges for

onsite resources and call-off resources?

No, Visa charges will not be paid by

CTBTO

13 Will CTBTO provide any VISA

assistance to the onsite/call-off

resources?

No, CTBTO will not provide any Visa

assistance for call-off resources.

14 What would be the approximate ratio of

simple, medium, complex categories out

Please refer to the 5 sample tickets and

to the ticket overview on sheet



___________________________________________________________________________

Page 3 of 4 7/26/2018

of 100 tickets in remote support? "Remote_Support_Tickets", attached

to this clarifications. The summary,

issue type, and label information can

give you an indicator of the expected

complexity.

15 What would be the minimum and

maximum onsite duration for call-off

resources?

For service 2.2. "Call-Off Resources"

the minimum onsite duration is one

day and the maximum duration should

not be more than 10 business days

(only in exceptional cases a longer

period might be required).

16 Please clarify whether bidder needs to

quote fixed cost for onsite and remote

support OR Time and Material rates to

be quoted?

Please provide a lump sum proposal

for Services 2.1. "Onsite Support" and

2.3 "Remote Support" (i.e. no Time

and Material rates).

17 Could you please arrange to share with

us with a few examples of JIRA tickets

and oblige. These examples will

facilitate a better understanding of the

tickets flow and complexities.

Please find attached 5 Jira sample

tickets.

18 I refer to attachment 1; 3.4 Service 2

“Call-off Resources”, page 12/53 of the

RFP. Did we understand correctly that

you need a detailed CV for every SAP

topic that we offer as “Call-Off

Resource”? Due to the large number of

experts, is it sufficient for you if we will

list the modules / topics we offer? Or

can you specify exactly what resources

you need?

As listed in 3.4 in Attachment 1 please:

- Describe the functional scope of SAP

profiles (e.g., SAP Mobile, SAP Hana,

SAP Data Modelling, SAP Payroll,

SAP GRC, SAP Year End Closing)

that you can offer as Call-off

Resources.

- Describe in detail the qualifications

and experience of the proposed

personnel.

This does not imply to send CVs for

every SAP expert, but to provide a list

of topics covered in the functional

scope and a set of minimum

qualifications and experience that the

proposed personnel will have.

19 I refer to Annex B;

2.1 “Onsite Key Personnel” & 2.3

“Remote Support” page 46/53 of the

RFP. Can you please confirm that the

SLA applies to both onsite and offsite

resources?

The SLA listed in Section 2.3 “Remote

Support” applies to Service 2.3

“Remote Support”.

Service 2.1 will be managed separately

and service levels may be different

depending on assigned activities and

priorities.

20 I refer to Annex B;2.5 “System

Upgrade Support”, page 49/53 of the

RFP. Can you confirm that you

understand under “System Upgrade”

e.g. an upgrade from EHP 7 to EHP 8?

What do you have for a system

landscape (3 or 4 system landscape)?

Can you provide us an EWA or a

A system upgrade is considered to be a

major enhancement such as an EHP

upgrade. Please find attached the

requested landscape information (“SAP

Systems”).



___________________________________________________________________________

Page 4 of 4 7/26/2018

graphic of your system landscape

(release, CPU, storage, etc.)?

21 Do we understand correctly that we will

use the CTBTO ticket system (JIRA)?

Would it also be possible to use a

contractor-internal ticket system?

The ticket system for communication

shall be CTBTO’s Jira system. The

Contractor may use an internal ticket

system for internal processing, but

shall interact with end users and

communicate results via CTBTO’s Jira

system. If possible, an interface

between the ticketing systems can be

implemented.

Count of Key Column Labels

Row Labels BASIS Finance HR Supply Chain Mgmt TRAVEL Grand Total

2017-1 40 15 8 12 1 76

2017-2 23 11 3 8 7 52

2017-3 26 6 6 9 15 62

2017-4 16 4 11 1 8 40

2017-5 27 7 11 4 11 60

2017-6 22 15 8 12 12 69

2017-7 49 6 9 10 10 84

2017-8 40 8 7 3 16 74

2017-9 45 11 12 9 8 85

2017-10 42 10 8 7 8 75

2017-11 51 10 5 5 9 80

2017-12 57 4 7 4 9 81

2018-1 84 9 9 10 2 114

2018-2 56 5 7 6 6 80

2018-3 55 8 8 9 4 84

2018-4 84 8 5 15 6 118

2018-5 64 10 11 12 7 104

2018-6 40 6 18 6 6 76

2018-7 41 6 10 8 4 69

Grand Total 862 159 163 150 149 1483

0

10

20

30

40

50

60

70

80

90

20

17

-1

20

17

-2

20

17

-3

20

17

-4

20

17

-5

20

17

-6

20

17

-7

20

17

-8

20

17

-9

20

17

-10

20

17

-11

20

17

-12

20

18

-1

20

18

-2

20

18

-3

20

18

-4

20

18

-5

20

18

-6

20

18

-7

BASIS

Finance

HR

Supply Chain Magmt

TRAVEL

Statistics

Summary Component/s Issue Type Labels

TDIP based on 9BS4 HR Configuration Fix insurance

VKAZ 2017 (2) PO 49-1875 not in GM commitments Finance Q&A gm_commitments

VKAZ 2017 PO Commitment Difference Finance Q&A gm_commitments

GL 630100 to derive CI TCIother Finance Q&A derivation_rule

Please clarify 10% threshold for PO lines Supply Chain Magmt Q&A po_amount_exceeding_pr_amount

Payroll posting - wrong fund/segment HR Q&A retroactive

Phone number not showing on PO printout Supply Chain Magmt Q&A po_printout

Payroll error for s/m 909571 HR Configuration Fix wagetype_GL_mapping

Education grant - eligibility for boarding without Special education grant HR Q&A ed_grant

Maintain AVC Table Finance Q&A sponsored_program_groups

Payslip shows wrong amount of both EG Claim (Settlement) and EG Advance Recovery HR Q&A ed_grant

EG Claim not reflect in payroll simulation - SM 800231 HR Q&A ed_grant_proration

Unable to settle the EGs due to period is greater than customized value for length P0965-BEGDA HR Configuration Fix ed_grant_settlement_date

Incorrect education grant advance recovery in IT0965 HR Configuration Fix ed_grant_advance_recovery

EOSA eligiblity HR Configuration Fix eosa

posting error GS - May 2018 payroll HR Q&A fix_exchange_rate_difference

Incorrect spouse allowance GS staff HR Configuration Fix spouse_allowance

Incorrect education grant claim - SM 8701324 HR Configuration Fix ed_grant

Transfer of fund / segment balances to GF Finance Q&A fund_segment_balance_transfer

Wrong vendor in print preview for SC 1000021983 Supply Chain Magmt Configuration Fix sc_print_version

OA not linking to release order Supply Chain Magmt Configuration Fix link_release_orders_to_oa

Creation of new segment VEUG Finance Master Data new_segments

PO Commitments Difference Finance Q&A gm_revaluation

Incorrect repatriation grant recovery for SM 945835 in Apr-2018 payroll HR Configuration Fix repatriation_grant

WBS settlement rules limited under profile Z30 Finance Configuration Fix settlement_rules

Not able to change digits in SAP Supply Chain Magmt Configuration Fix correct_currency

Error when Parking invoice #5105617864 Finance Configuration Fix transport_error

Retroactive child allowance due to depented spouse HR Configuration Fix child_allowance,, dependent_spouse

MIGO error message Finance Configuration Fix regenerate_fi_validation_and_subst_rules

DOC.5105617688, PO lines 20,30 are blocked Finance Configuration Fix asset_value_date

Settling-in Grant on payslip after advance payement received HR Q&A settling_in_grant

Discrepancy between ZBUDCON and FMCEMON01 Finance Q&A report

Fiscal Year 2019 Finance Configuration Fix po_for_subsequent_year, year-end

ZSCR019 report and missing info. Supply Chain Magmt Configuration Fix report

Correct Settling-in Grant HR Configuration Fix settling_in_grant

Incorrect calculation for Settling in grant for Dependent Spouse HR Configuration Fix settling_in_grant

Report Painter error Finance Q&A report

PDF engine settings in SAP Supply Chain Magmt Q&A print_format

PBC Error VEUF related - Feb 2018 Payroll HR Q&A pbc_error_with_gm

Approval note from SC disappeared Supply Chain Magmt Configuration Fix approvers_on_sc_printout

Dep child allowance GS int s/m 821014 - Feb 2018 payroll HR Configuration Fix dep_child_allowance

Can't create a posting run Finance Q&A carry_budget_forward, year-end

Reimbursable tax not updating on MISC PO (ZMUR) Printout Supply Chain Magmt Q&A update_tax_in_pos

Error message - Annual Budget exceeded Finance Q&A budget_exceeded

Balancing field "segment" in line item 001 not filled Finance Q&A incorrect_set_entry

Parked document 5105617274 Finance Q&A posting_period

Post Adjustment Multiplier for February 2018 payroll HR Master Data pam

Remote Support Tickets

Wrong USD amount in PR release e-mail notification Supply Chain Magmt Configuration Fix release_email

Negative commitments in ZDonor reports Finance Configuration Fix close_veuf_travel_commitments

Asset mass change options BASIS User & Role maintenance role_change

ZSCR019 report could not be run Supply Chain Magmt Q&A report

MI07 posting Physical Inventory differences - errors Supply Chain Magmt Q&A correct_cost_center

Payroll - JAN 2018 wrong HR Configuration Fix transitional_allowance

Rental subsidy Threshold for s/m 8700433 HR Configuration Fix rental_subsidy

Change of SC type in ME52N for role Chief, Procurement Supply Chain Magmt Q&A change_sc_type

Authorization Group Finance Q&A posting_period

Dep child allowance GS s/m 801616 HR Configuration Fix dep_child_allowance

Dep child allowance for 2017 wrongly calculated HR Q&A unclear_solution

Payslips for PS staff show wrong amount of dep. children when child is adopted. HR Configuration Fix dependency_allowance

Employee Subgroup update HR Configuration Fix employee_subgroups

Settling In Grant based on EUR DSA instead of USD DSA HR Configuration Fix settling_in_grant

Correct the numer of dependet children HR Configuration Fix dep_child_allowance

Error message when adding an expense to a recalled Approved TR-3204 TRAVEL Q&A expense_report_timing, year-end

Error message when generating cover eligibility rule Finance Q&A posting_address, year-end

2017 FMOD access BASIS User & Role maintenance fmod, year-end

POs Not Appearing In Inbox Supply Chain Magmt Q&A missing_workitems, year-end

Updating value of VIC asset Finance Q&A vic_asset, year-end

2018 Appropriation Finance Q&A report, year-end

Release strategy in POs for newly added SSJ not working! Supply Chain Magmt Master Data release_strategy

Expense reports workflow TRAVEL Configuration Fix hr_tv_workflow

Data in Fgi3 Report (ZstateII4) Finance Q&A report

Station report Finance Q&A report

Payroll postings are wrong f. August 2017 HR Configuration Fix ed_grant_proration

Credit not taken into account Finance Q&A correct_tr_credit_note_posting

SAP EnvironmentSID Hostname System Type in the Landscape vCPU's RAM Provisioned Space (GB)

SAP ECC CBD CTBTOSAPCBD Sandbox - Copy of CEP 2 16 999.13

CED CTBTOSAPCED Development 2 24 846.13

CEQ CTBTOSAPCEQ Quality 2 24 864.18

CEP CTBTOSAPCEP1 Production 4 32 1310.72

CEP - DR CTBTOSAPCEPDR Disaster Recovery 2 8 1064.96

SAP SRM CSD CTBTOSAPCSD Development 2 16 418.13

CSQ CTBTOSAPCSQ Quality 2 20 405.13

CSP CTBTOSAPCSP1 Production 4 32 957.18

CEP - DR CTBTOSAPCSPDR Disaster Recovery 2 8 748.13

Sol. Man SSD CTBTOSAPSSD 2 24 684.13

Portal EBD CTBTOSAPEBD Development 4 32 382.13

EBQ CTBTOSAPEBQ Quality 2 24 474.13

EBP CTBTOSAPCPP1 Production 4 32 787.18

EBP-DR CTBTOSAPEBPDR Disaster Recovery 2 8 758.13

SAP ConnectSAP-WTS CTBTOSAPMEDIA SAP Service Connection 2 4 244.13

Total 12 38 304

SAP Systems

[WAR-4385] Outline Agreement not linking to release order Created: 15/May/18 Updated: 29/May/18 Due: 16/May/18 Status: Closed

Project: CORE Support

Component/s: Supply Chain Mgmt Type: Configuration Fix Priority: High

Reporter: xxx Assignee: xxx

Labels: link_release_orders_to_oa Attachments: Amd#2 CO 2008-0410.PNG Amd#3 CO 2008-0410.PNG

image-2018-05-15-17-42-20-386.png image-2018-05-15-17-43-05-444.png image-2018-05-15-17-44-24-411.png image-2018-05-15-17-46-36-363.png image-2018-05-24-15-05-54-248.png image-2018-05-28-10-12-26-656.png image-2018-05-28-17-21-15-715.png screenshot-1.png screenshot-2.png Test in CED120 - OA linked to PO.docx

In progress time - xx:

6d 18h 39m

Last comment: Dear xxx, I can confirm that it works in CEP100 (see attached screenshot). Regards, xxx !screenshot-2.png|thumbnail!

Solution: Solved by xx

Closed date: 28/May/18 5:35 PM Description

Dear xxx,

Refer to Outline Agreement (OA) 5100000010 (Amendment No. 3 to Contract No. 2008-0410) and OA MOA0000074 (Amendment No. 2 to Contract No. 2008-0410). It is not possible to link release orders to OA 5100000010, i.e. the CTBTO contract number 2008-0410 and release number do not show on the relevant fields when linking to the OA.

Note that the SAP field Amendment No. shows "2" in OA 5100000010 although it should be "3". (MOA0000074 also shows "2" in the amendment no. field). Both OAs are correctly linked to 2008-0410 in the original PO/contract no. field.

See also screenshots.

Regards, xxx

Comments

Comment by xxx [ 15/May/18 ]

UPDATE:

PLEASE CHANGE THIS TO HIGH PRIORITY SINCE IT DOES NOT WORK TO CREATE A CONTRACT REFERENCE AND FRD NUMBER WITH MOA0000074, AS WELL! SOMETHING HAS HAPPENED SINCE THE RELEASE OF OA 5100000010 CAUSING THIS PROBLEM, PERHAPS BECAUSE THE INITIAL DOCUMENT IS A MIGRATED DOCUMENT?

Regards, xxx


Dear xxx,

If I understand well your request when you perform the contract release order starting from the OA 5100000010, in the PO POFR some information are not retrieved.

I have tried in CED120 environment to replicate the case using OA 5100000010. OA 5100000010 has “Original PO/Contract No” 2008-0410. OA 5100000010 and OA MOA0000074 (migrated OA) have “Original PO/Contract No” 2008-0410.

Please find the steps below:

1.Run transaction ME33K and insert OA 5100000010

2. Click on Contract --> Follow on Functions --> Contract Release Order

3. I moved the OA item 10 in PO type POFR

4. The PO fields are filled with OA values

If my understanding is correct please let me know which fields you noticed that are not copied from OA to PO.

Otherwise, please provide the steps you performed in order to replicate the case.

Thank you

xxx


Dear xxx,

That is not how we process release orders when we have many items, i.e. manually search for items and drag them in one by one, then manually link them to each PR line one by one. The way we have been working with for years (although the above described method can also be used) is to select FRD as the PO type, drag in all PR lines and then link to the OA line items (note: the current system setup only requires the 1st line to be linked actually). This approach works for other OAs, only this one not. Since both documents have Amendment 2 (which is wrong), I think this is related to the migrated OA causing some issued.

Regards, xxx


Dear xxx,

Thank you for your feedback. I tried to replicate the same case in CED120 environment and in PO type POFR the field “CTBTO PO/Contract no” is correctly retrieved when I link OA. I create a PO type POFR and I drag in the PR. Then I link OA similar to the one you mentioned (same "Orig. PO/Contract no" and "Amendment No"). The field "CTBTO PO/Contract no" of PO is retrieved from OA and it seems that the same "Amendment No" doesn't influence the fields derivation. Please find the steps that I performed in the file word attached “Test in CED120 - OA linked to PO”.

Please let me know if you perform different steps and if you can, please provide some screenshot of your case.

Thank you Kind regards xxx

Comment by xxxs [ 23/May/18 ]

Dear xxx,

Steps: 1. Open ME21N

2. With POFR as the PO type selected, drag in approved PR 10010924 into the PO. 3. Link at least first line to latest OA document, i.e. latest contract amendment which is OA 5100000010, which will generate the original contract no. to 2008-0410 and the release order number. 4. Insert at least the mandatory fields so that the PO can be saved 5. Save PO and open it again 6. The contract no. of the OA (2008-0410) is not inserted in the CTBTO contract number field as it should be, AND no release number is generated. Please refer to the attached screenshot. This is how FRDs have been prepared for years.

Regards, xxx

Update: until this is solved, I will use the ZMM_UPLOAD transaction to manually insert the correct contract number and release number.


Dear xxx,

Thank you for your feedback.

I replicated the case in development environment and the issue about missing PO fields derivation occurs when OA is not inserted in the first PO item.

In other words when OA is inserted in the first PO item, PO fields "CTBTO PO/Contract no" and "Release no" are correctly retrieved; when OA is inserted in the next PO items the PO fields are not retrieved from OA.

In PO 4800001129 the OA 5100000010 has been inserted in PO item 20 and PO fields "CTBTO PO/Contract no" and "Release no" are not retrieved.

If OA 5100000010 was inserted in PO item 10 the fields "CTBTO PO/Contract no" and "Release no" were retrieved.

We have involved our technical team in order to retrieve the OA information when it is inserted in any PO items.

In the meanwhile you can insert the OA in the first PO item in order to retrieve the OA information correctly.

I will keep you informed

Please let me know if any clarification is needed

Kind regards

xxx


Dear xx,

Sorry, I must have overlooked that the PO for some reason had the first line "hidden" at the top and I did not check the item number to the left (probably because the 2nd line highlighted a message so the cursor was set there). Thank you for implementing that in any case!

Regards, xxx


Dear xxx,

We have implemented a change in the logic in order to retrieve the PO fields "CTBTO PO/Contract no" and "Release no" when the OA is inserted in any PO items. Before changes, the PO fields "CTBTO PO/Contract no" and "Release no" were retrieved only if OA was inserted in the first PO item.

Please consider PO 4800000937 in CEQ220.

OA 5300000040 has been inserted in PO item 30 and "CTBTO PO/Contract no" and "Release no" have been correctly retrieved from OA.

Please let me know your feedback and if we can ask the transport in production.

Thank you

xxx

Comment by xxx[ 28/May/18 ]

Dear xxx,

This looks fine in CEQ. Please provide xxx with the transport numbers. Thanks.

Regards, xxx


Dear xxx,


Dear xxx,

Could you kindly transport to CEP the following TR:

Sq. Nr. TR Number TR Owner TR Description TR Type

1 CEDK910246 xxx WAR-4385 OA not linking to release order Workbench

Please feel free to contact me for any clarification.

Thank you

Kind Regards

xxx

Comment by Mxxx [ 28/May/18 ]

Dear xxx,


Dear xxx,

The TR has been transported to CEP100.

Thanks and regards

xxx

Comment by xxxs [ 28/May/18 ]

Dear xxx,

I can confirm that it works in CEP100 (see attached screenshot).

Regards, xxx

Generated at Thu May 31 10:46:56 GMT 2018 by xxx using JIRA 7.8.0#78000-sha1:4568b9d484113d74dfb6f152fb925b5fa1be2ef7.

[WAR-4072] Error message - Annual Budget exceeded Created: 07/Feb/18 Updated: 16/Feb/18 Status: Closed


Component/s: Finance Type: Q&A Priority: Medium


Labels: budget_exceeded Attachments: error 5105617332.docx image-2018-02-07-11-30-33-949.png

image-2018-02-12-15-09-27-048.png image-2018-02-12-15-10-08-197.png image-2018-02-12-15-11-19-200.png image-2018-02-12-15-20-28-440.png

In progress time - XXX:

4d 1h 59m

Last comment: Dear xxx, Thank you so much for the explanation. Kind regards, xxx

Solution: Solved by XXX

Closed date: 16/Feb/18 5:50 PM Description

Dear Colleagues,

Kindly find invoice doc. number 5105617332. PO 2017-1949; SAP 4400000151, LOG 40866

It shows error message while saving the invoice as completed. Please see attached.

• Annual Budget exceeded by 5,152.97 USD Message N. FMAVC008*

Please assist with this issue. Thank you in advance. Kind regards, Xxx

Comments

Comment by xxx [ 07/Feb/18 ]

Dear Xxx,

could you kindly save the Parked Invoice and exit from the document so we can analyze it?

Many Thanks in advance.

Kind Regards,

Xxx


Dear Xxx,

would you mind updating the status of this ticket?

kind regards

Xxx


Dear Xxx,

I've checked the status of the invoice doc. 5105617332 and it shows the same error massage. Annual Budget exceeded by 5,152.97 USD Message N. FMAVC008*

Please assist. Thanks and regards, Xxx

Comment by xxx[ 12/Feb/18 ]

Dear Xxx,

kindly be informed that we have checked the invoice doc. 5105617332 and the error is due to the Exchange Rate difference occurred between the Good Receipt and the Invoice.

The PO has been saved with the exchange rate eur/usd fixed at 0,837, as consequence the GR has been posted with the same ROE. It means that total amount of 108.500 EUR correspond to 129.629,63 USD (108.500 / 0,837).

In the invoice, instead, has been entered as Posting Date the 07.02.2018, when a new ROE has already occurred (0,805):

Therefore, the total amount 108.500 EUR is now equal to 134.782,61USD.

The difference between the old value in USD and the new one (134.782,61 - 108.500 = 5.152,99 USD) is exactly the amount triggered in the "Annual Budget exceeded" error. The error is triggered because the system is trying to allocate this additional amount on the Asset Account, but there is no budget available on this specific combination of Account Assignment (Available Budget - Posting amount = 0 - 5.152,99 = -5.152,99):

In order to solve this issue there are two possible solutions to be evaluated:

1. As mentioned in JIRA WAR-4022, the ROE difference of the Asset Account should be allocated on the Exchange Rate GL Account 163000, as already happens for Material and Service Accounts. At the moment for a reason we haven't identified yet this substitution doesn't occur for some Asset Invoices. Therefore, we have opened a

OSS Message in order to analyze these cases with the help of SAP. As soon as they provide us a proper reply we will understand how to manage also these particular cases.

2. The ROE is triggered by the date entered in the Posting Date, so you can change this date in a previous period where the other ROE (0,837) was still in use. In this way, the invoice will be created without any Exchange Rate difference. For example you can enter as Posting Date the "31.01.2018", that is still opened in the FI Posting Periods.

Kindly Let us have your feedback. Many Thanks,

Best Regards

Xxx


Dear Xxx,

I've tried the second solution, changed the posting date to 31.01.2018, but it still shows the same error message as before. kind regards, Xxx


Dear Xxx,

As discussed, I have deleted DOC. N. 5105617332 (invoice log 40866) and parked new invoice under Doc. 5105617415 with the posting date 31.01.2018. The invoice was created without any exchange rate difference. The issue is resolved. You can close the ticket.

Thank you very much for your assistance and help! Kind regards, Xxx


Dear Xxx,

would you please document if there is the addional action you have taken to resolve the issue?

Thanks and regards

Xxx


Dear Xxx,

kindly be informed that there are no further action taken.

The issue has been solved creating again the invoice with the Posting Date equal to 31.01.2018.

Kind Regards,

Xxx


Dear Xxx,

Thank you so much for the explanation.

Kind regards,

Xxx Generated at Thu May 31 10:55:21 GMT 2018 by xxx using JIRA 7.8.0#78000-sha1:4568b9d484113d74dfb6f152fb925b5fa1be2ef7.

[WAR-4135] Incorerct calculation for Settling in grant for Dependent Spouse Created: 27/Feb/18 Updated: 05/Mar/18 Due: 02/Mar/18 Status: Closed


Component/s: HR Type: Configuration Fix Priority: Medium

Reporter: XXX Assignee: XXX

Labels: settling_in_grant Attachments: image-2018-02-27-10-34-51-477.png image-2018-02-27-10-35-

11-699.png image-2018-03-01-11-37-36-532.png image-2018-03-01-11-43-46-175.png image-2018-03-01-11-47-11-948.png image-2018-03-01-11-47-31-542.png


1d 22h 58m

Last comment: Dear XXX, I have checked in CEP100 and all is fine:


Closed date: 01/Mar/18 11:48 AM Description

Dear xxx,

The Settling in grant for SM (831917) spouse who arrived in January is not calculating correctly. It appears to be calculated two times. Please see the screen shots below:

Regards,

XXX

Comments

Comment by XXX [ 01/Mar/18 ]

Dear XXX,

We fixed the issue in the custom method for the Settling in Grant Dependent.

The changes are ready for your test in CEQ 220.

Please let us know your feedback.

Thanks & Regards,

XXX


Dear XXX,

The calculation is correct in CEQ220. Will you transport this to CEP100?

Many thanks,

XXX


Dear XXX,

Thanks for feedback.

Dear XXX,

Please move to CEP the following TRs with this order:

CEDK909924 - EVE: artf6058251 WAR-4135 Incorerct calculation for Settling

CEDK909928 - EVE: artf6058251 WAR-4135 Incorerct calculation for SetGD 2

CEDK909930 - EVE: artf6058251 WAR-4135 Incorerct calculation for SETGD 3

Thanks & Regards,

XXX


Dear XXX,

The TRs have been moved to CEP100.

Thanks and regards

XXX


Dear XXX,

I have checked in CEP100 and all is fine:

Kind regards,

XXX

Generated at Thu May 31 10:59:21 GMT 2018 by xxx using JIRA 7.8.0#78000-sha1:4568b9d484113d74dfb6f152fb925b5fa1be2ef7.

[WAR-4158] Fiscal Year 2019 Created: 06/Mar/18 Updated: 14/Mar/18 Status: Closed


Component/s: Finance Type: Configuration Fix Priority: Medium


Labels: po_for_subsequent_year, year-end Attachments: 2019 FY.docx image-2018-03-06-18-58-56-996.png image-

2018-03-09-13-45-54-757.png image-2018-03-13-08-42-10-713.png


Last comment: Dear xxx, The Issue is resolved now. Thank you for our assistance. I'm closing the ticket. BR, Xxx


Closed date: 14/Mar/18 8:58 AM Description

Dear Xxx,

When one of our Divisions tries to initiate the SC for 2019 the system gives them the error message (please find attached)

Please advise.

Thank you,

Xxx

Comments

Comment by xxx [ 06/Mar/18 ]

Dear Xxx,

kindly note that this error is related to the closure of the FM posting periods.

From your screenshot we notice that you are trying to post a Purchase Requisition (Value

Type = 50) in 2019.

The FM Posting Period are maintained in transaction FMIR.

Our User ID is not authorized accessing it in CEP but we double checked data in the table FMIUR (Open Interval Rules for updating FM).

In 2019 it is not allowed posting any transaction, since no record exists:

We are going to open relevant time interval in Development environment and then we will release it to you in CEQ for your verifications.

Before start changes, would you confirm if the Value Type 50 "Purchase Requisition" for which you faced the error is the only one that you need to be opened in 2019?

Thanks in advance for your reply.

Kind Regards,

Xxx

Comment by Xxx [ 07/Mar/18 ]

Dear Xxx,

Please open it for the Value Types 50 and 51.

Thank you,

Xxx


Dear Xxx,

Please be informed that the necessary data have been maintained in FMIR transaction and saved in the TR CEDK909964.

It has been moved in CEQ for your verifications before importing in CEP.

In addition, please note that in order to let you creating Purchase Requisition you need also to maintain the transaction FMBOSTAT.

This has been just performed during the Year-End Closing and Fiscal Year Change activities for Year 2018, same should be done for Year 2019.

That activity is in charge of you, as described in the shared guide “FI-FM-GM Annual Closure - Year-End Closing and Fiscal Year Change_User Guide_v1 0_14 12 2017.docx” (saved in the WAR-3860).

Please find below an extract about this point (paragraph 2.11). More details are available in the document:

Through FMBOSTAT transaction users maintain the combination of budget version and

budget status for each fiscal year, where: __

• Version represents an indicator of the available budget. In CTBTO only budget in version 0 can be spent.

• Budget status represents a specific stage of the budgeting lifecycle.

In this transaction it also possible to define Budget address check, if this indicator is set, then only the FM account assignments that were explicitly defined as budget addresses can be used for budgeting

This activity is accounted to the user.

Finally:

• the changes in FMIR have been performed by us and are currently in CEQ. As soon as you will give us your approval we will suggest to Xxx importing in CEP

• the changes in FMBOSTAT are in charge of you. You can follow the User Guide available in WAR-3860.

Should you need any further support from our side please feel free to contact us.

Thank you.

Kind Regards,

Xxx


Dear Xxx,

Yes, please go ahead with the importing the changes to CEP.

Thank you,

Xxx


Dear Xxx,

thank you for feedback.

Dear Xxx,

following Xxx's approval, would you kindly import in CEP the TR CEDK909964 "WAR-4158 - Fiscal Year 2019 - Opening FM Posting Periods" ?

For further information, please feel free to contact us.

Thank you very much.

Kind Regards,

Xxx

Comment by xxx [ 09/Mar/18 ]

Dear Xxx,

The TR CEDK909964 has been transported to CEP.

Kind regards

Xxx


Dear Xxx,

We usually run the transaction FMBOSTAT as a part of year opening exercise. For example for 2018 FY we run it in January 2018. But we were able to raise and approve SCs with 2018 FA in 2017.Could you please clarify why for FY 2019 we are doing it now?

Thank you,

Xxx


Dear Xxx,

please be informed that last year, in the beginning of 2017, we have suggested you to add Version 0 for 2018 in the transaction FMBOSTAT as well, in order to allow you to create Shopping Carts for 2018 already. This year you should perform the same action in order to allow you to create SC in 2019.

We had also update the related User Guide last year with this step.

Please feel free to contact us for any further clarification.

Many Thanks and Kind Regards,

Xxx


Dear Xxx,

Does it mean that I will run this transaction twice, now and in 2019?

Thank you,

Xxx


Dear Xxx,

you can now enter the Version 0 for 2019 in FMBOSTAT, while in the beginning of next year you can insert all the remaining lines for 2019 and the Version 0 for 2020.

I can confirm that you have to execute it twice now but then if you keep doing as highlighted above, for the next years you can execute it only once in the beginning of the year.

Kindest Regards,

Xxx


Dear Xxx,

The Version 0 for 2019 has been added*.* Please see below*:*

Thank you,

Xxx


Dear Xxx,

very good, then there should be no issues anymore in creating the SCs and POs for 2019.

Kindly let us know if you need further support.

Many Thanks,

Xxx


Dear Xxx,

The Issue is resolved now. Thank you for our assistance. I'm closing the ticket.

BR,


[WAR-4338] Creation of new segment VEUG Created: 02/May/18 Updated: 08/May/18 Status: Closed


Component/s: Finance Type: Master Data Priority: Medium

Reporter: Xxx Assignee: Xxx

Labels: new_segments Attachments: CTBTO_Realisation_CSD_FI_v3.3_04.05.2018.docx

fm_training_manual_vs_1.2-_august_2014.docx image-2018-05-07-11-55-39-488.png image-2018-05-08-10-16-59-832.png WAR-4338 - How to create a new Segment_04.05.2018.docx


17h 55m

Last comment: Thank you Xxx and XXX! Have a nice day. Xxx


Closed date: 02/May/18 10:32 AM Description

Dear XXX,

Please kindly create new segment VEUG.

Fund: VEUG

Name: EU VC VII

Description: EU Voluntary Contributions VII

Thank you and have a nice day.

Xxx

Comments

Comment by Xxx [ 02/May/18 ]

Dear Xxx,

Would you please kindly create the fund?

Thanks and regards

Xxx


Dear Xxx,

Xxx just created the fund. Thank you.

Xxx


Dear XXX,

Please send us the detail instruction to create Segment.

Thanks and regards

Xxx


Dear Xxx,

please be informed that the Segment should be created in customizing and therefore it is in charge of XXX.

We have just created the Segment VEUG and the changes are available in CEQ for testing.

Kindly let us know when we can import it in production.

Kindest Regards,

Xxx


Dear Xxx,

Thanks for the information. We still would like to know the customization steps and documented.

Regards

Xxx


Dear Xxx,

please find in attachment a small User Guide in which there are described the customizing steps for creating a new Segment.

Kindly find also in attachment the updated CSD for Finance.

Kindest Regards,

Xxx


Dear Xxx,

Thanks a lot for the documentation and customization actions.

Dear xxx,

Please kindly confirm if we can move the Segment VEUG to production system or not.

Thanks and regards

Xxx


Dear Xxx,

I can't do test in CEQ 900, as Fund VEUG is not there.

From the screenshot in the attachment, it shows the corrected name and correct description. It looks fine to me to be moved to production.

Thank you very much for your help.

Xxx


Dear Xxx,

Please let us know the Transport request number.

Thanks and regards

Xxx


Dear Xxx,

please be informed that changes have been saved into customizing TR:

CEDK910190 xxx "WAR-4338 - New Segment VEUG - 04.05.2018"

For any additional clarification please feel free to contact us.

Thank you.

Kind Regards,

Xxx


Dear xxx,

The Transport request for segment VUEG has been moved to CEP100.

Thanks and regards

Xxx


Thank you Xxx and XXX! Have a nice day.


clarifications no. 2: rfp no. 2018-0092/jibril · 2018. 7. 26. · clarifications no.2: rfp no....

Documents