Data load problem in Payroll Cube - BW 3.5

[Former Member]

Dear all,

I am trying to load HR-Payroll cube 0PY_C02 from the datasource 0HR_PY_1 (in BW 3.5). Test extraction (RSA3) shows data in the source system. This is the first time a load has been run between the BW and the mentioned source system.

The request turns green but doesnt fetch any record (is successful with zero records).

Anyone has any idea what might be causing this. Have I missed some step in the BC activation? But the Cube, Transfer rules and the update rules are all active.I had to include a custom infoobject which is a compounding attribute of 0Employee in the cube, infosource.

Will surely award points for useful answers.

Regards

Pradyut.

[Former Member · Accepted solution]

For Payroll extractor you have do the config for BW Payroll month assignment. This setting is for payroll results consolidation ( INPERIOD or FORPERIOD with contry specific).

Secondly if are not getting data even you have some valid results in RT cluster, check the authrization for background user ALEREMOTE. You have added some additional profiles for HR Data extraction as per your system release.

Check OSS note 150315.

Hope it helps.

Regards

[Former Member · Accepted solution]

Dear paolo,

Thanks for your answer. I have already done the config for the BW Payroll month assignment in SBIW in R/3.

The second option seems more likely in this case. Can you throw some light on exactly which authorizations are required for user ALEREMOTE. Also please could you explain in little more detail your last sentence "You have added some additional profiles for HR Data extraction as per your system release."

Thanks

Pradyut

[Former Member · Accepted solution]

From SAP Note:

Reason and Prerequisites

a) In the BW there exist two user:

i) a human administrator, using S_RS_ALL

ii) a user called BWREMOTE (or similar), used to receive the data

from the OLTP, using S_BI-WHM_RFC

b) In the OLTP there exist also two user:

i) a human administrator, needing authorizations to create users

and RFC-destinations.

ii) a user called ALEREMOTE (or similar), used to ...

1) ... connect the OLTP to the BW

2) ... extract the data

3) ... send the data to the BW

4) ... show monitoring dialogs

for tasks 1 to 4, the profile S_BI-WX_RFC is used (however does

not suffice on some points since some authorizations are

missing in the delivered profile)

5) ... make customizing of OLTP extractors

for this, additionally the authorizations to execute

IMG-functionality, to execute Transaction SBIW and

to maintain the applications, which shall be customized, must

be given during the customizing functionality is used.

Solution

1) The profile S_RS_ALL resp. S_BI-WHM_RFC must contain (at least)

the following authorizations:

Profile

--- S_BI-WHM_RFC <PRO> Business Information Warehouse, RFC user in

-- B_ALE_ALL <PRO> All authorizations for ALE/EDI

-- S_BI-WHM_SPC <PRO> Business Information Warehouse, special

-- S_ADMI_FCD <OBJ> System Authorizations

--- S_ADMI_ST0R <AUT> ST0R

-- S_DATASET <OBJ> Authorization for file access

--- S_DATASET_AL <AUT> All File Accesses Allowed

--- S_IDOCCTRL <OBJ> WFEDI: S_IDOCCTRL - General Access to

--- S_IDCCTR_ALL <AUT> All auths. for IDoc functions

-- S_BTCH_ADM <PRO> BC: Batch - Processing authorization

-- S_BW_RFC <PRO> BW: Authorization Profile: Other

-- PLOG <OBJ> Personnel Planning

--- P_PLOG_WF_DI <AUT> Display Authorization for PD

-- S_ADMI_FCD <OBJ> System Authorizations

--- S_WF_RFCDEST <AUT> Display RFC Monitor for WF_LOCAL

--- S_ADMI_FCD <FLD> System administration function

NADM

-- S_CTS_ADMI <OBJ> Administration Functions in Change and

--- S_CTS_TABL <AUT> CTS_ADMFCT = TABL

--- CTS_ADMFCT <FLD> Administration Tasks for

TABL

-- S_DATASET <OBJ> Authorization for file access

--- S_BW_RFC <AUT> Authorization for Delta Upload

-- ACTVT <FLD> Activity

*

-- FILENAME <FLD> Physical file name

*

--- PROGRAM <FLD> Program Name with Search Help

SAPMS38L

-- S_DEVELOP <OBJ> ABAP/4 Development Workbench

--- S_SUBMIT_ALL <AUT> Execute All

-- ACTVT <FLD> Activity

16

-- DEVCLASS <FLD> Package

*

-- OBJNAME <FLD> Object name

*

-- OBJTYPE <FLD> Object type

PROG

--- P_GROUP <FLD> Authorization group ABAP/4

*

-- S_LOG_COM <OBJ> Authorization to execute logical

--- S_LOGCOM_ALL <AUT> Auth. to execute all logical

-- S_OC_DOC <OBJ> SAPOffice: Authorization for an

--- S_OC_ALL <AUT> All authorizations

-- S_OC_ROLE <OBJ> SAPoffice: Office User Attribute

--- S_OC_ALL <AUT> All Authorizations

-- S_OC_SEND <OBJ> Authorization Object for Sending

--- S_OC_ALL <AUT> All send authorizations

-- S_PROGRAM <OBJ> ABAP: Program Flow Checks

--- S_SUBMIT_ALL <AUT> Execute All Programs

-- P_ACTION <FLD> User action ABAP/4 program

SUBMIT

--- P_GROUP <FLD> Authorization group ABAP/4

*

-- S_RFC <OBJ> Authorization Check for RFC Access

--- S_RFC_ALL <AUT> Execute all function modules via

-- S_RZL_ADM <OBJ> CCMS: System Administration

--- S_RZL_ALL <AUT> Administration authorization

-- S_TCODE <OBJ> Transaction Code Check at Transaction

--- S_TCD_USER <AUT> Basis Transactions for End User

--- S_WF_WI <OBJ> Workflow: Work item handling

--- S_WF_WI_ALL <AUT> All authorizations for Workflow

-- S_IDOC_ALL <PRO> All authorizations for IDoc functions

--- S_RS_ALL <PRO> Business Information Warehouse: All

2) The referred functionality is b) i) 5), thus

the authorizations to execute IMG-functionality,

to execute Transaction SBIW and to

maintain the applications, which shall be customized,

must be temporarily given to ALEREMOTE, if you want to execute the

functionality from BW-side. The permissions for executing the

customizing is not included in the profile S_BI-WX_RFC, since

this is a critcal functionality.

However there is the possibility to execute the customizing

in the OLTP by a human administrator by hand, using Transaction

SBIW.

3), 4) For sending the Idocs and reading RFC-destinations

the profile S_BI-WX_RFC is incomplete.

Please check, if the following authorizations are included:

Profile

--- S_BI-WX_RFC <PRO> Business Information Warehouse, RFC User

-- B_ALE_ALL <PRO> All authorizations for ALE/EDI

-- S_APPL_LOG_A <PRO> Application log: All

-- S_BTCH_ADM <PRO> BC: Batch - Processing authorization

-- S_BW_RFC <PRO> BW: Authorization Profile: Other

-- See above, same sub-profile as in S_BI-WHM_RFC

--- S_IDOC_ALL <PRO> All authorizations for IDoc functions

- BW AddOn BW-BCT 1.2B:

These authorizations have been delivered with BW AddOn Patch 2 (see 158489 for the AddOn Patch information), except release 45B. For 45B, the authorizations are delivered with BW AddOn Patch 1.

- PI2000.1:

For 4.6B and 4.6C due to delivery errors, this profile also is incorrect. Please transport it from the BW into the Oltp (it is the same in any system and release).

- PI2000.2:

For 4.6C due to delivery errors, this profile also is incorrect.

Please transport it from the BW into the OLTP (it is the same

in any system and release).

- PI2001.2:

For 4.6C due to delivery errors, this profile also is incorrect.

Please transport it from the BW into the OLTP (it is the same

in any system and release).

Alternatively, import the sapserv* transport BRSK002208 under the directory
general\R3server\abap\note.0150315 into your OLTP-System.

For help on the sapserv* transport refer to Note 13719.

5) If you have PI-Basis 2005.1 in your source system, you need to attach role SAP_RO_BCTRA to your user in the source system. Otherwise, the functionality mentioned in the message is not available. The system continues to function as before, you may ignore the warning.

Regards

[Former Member · Accepted solution]

Dear Paolo,

Thanks again for that answer.

We have background user ALEREMOTEin both the systems.

In BW it has a SAP_ALL profile. So I thought there no issue of authorisation on this side.

However, as you too have mentioned, in R/3 ALEREMOTE has profile S_BI-WX_RFC. And as you say it is not sufficient all the time.But I checked the profile

S_BI-WX_RFC and it has all the authorizations you have mentioned below:

S_BI-WX_RFC <PRO> Business Information Warehouse, RFC User

|

|-- B_ALE_ALL <PRO> All authorizations for ALE/EDI

|-- S_APPL_LOG_A <PRO> Application log: All

|-- S_BTCH_ADM <PRO> BC: Batch - Processing authorization

|-- S_BW_RFC <PRO> BW: Authorization Profile: Other

--- S_IDOC_ALL <PRO> All authorizations for IDoc functions

Isnt the authorization object SAP_RO_BCTRA used for remote activation of datasources from BW? But that is anyway not applicable here because I manually activated the datasource in R/3. By the way, we are on PI-Basis 2005.1.

Any idea what might be causing the problem?

Just to add one more point, I am pasting below the job log of one of the succesful jobs that ran in R/3 corresponding to the loads I had run. It clearly says that the exits couldnt fetchany data from the source.I wonder why that is happening because RSA3 is positively showing data. Any idea, please let me know.

Job started

Step 001 started (program SBIE0001, variant &0000000000003, user ID ALEREMOTE)

Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)

DATASOURCE = 0HR_PY_1

*************************************************************************

• Current Values for Selected Profile Parameters *

*************************************************************************

• abap/heap_area_nondia......... 2000000000 *

• abap/heap_area_total.......... 2000000000 *

• abap/heaplimit................ 40000000 *

• zcsa/installed_languages...... KED *

• zcsa/system_language.......... K *

• ztta/max_memreq_MB............ 250 *

• ztta/roll_area................ 2000000 *

• ztta/roll_extension........... 2000000000 *

*************************************************************************

<b>Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 0 records

Result of customer enhancement: 0 records

Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 0 records

Result of customer enhancement: 0 records

IDOC: Info IDoc 2, IDoc No. 198026, Duration 00:00:00

IDoc: Start = 21.12.2006 10:31:56, End = 21.12.2006 10:31:56

Synchronized transmission of info IDoc 3 (0 parallel tasks)</b>IDOC: Info IDoc 3, IDoc No. 198027, Duration 00:00:00

IDoc: Start = 21.12.2006 10:31:58, End = 21.12.2006 10:31:58

Job finished

Regards

Pradyut.

[Former Member · Accepted solution]

Dear all,

Anyone has any idea regarding my current problem mentioned above?

If yes, please respond.

Will be more than happy to award helpful answers generously!!

Regards

Pradyut.

[Former Member · Accepted solution]

Hi,

Have you seen the notes:672514,964569,397208,329961 ?

With rgds,

Anil Kumar Sharma .P

[Former Member · Accepted solution]

To be sure on ALEREMOTE authorizations, login directly to R3 with this user and check extraction from RSA3; if there are authorization problem write /nsu53 in trx box and you'll get the auth.object needed.

Hope it helps.

Regards

[Former Member · Accepted solution]

Dear Anil,

Thanks a lot for your answer. The notes you mentioned, specially 397208 and 672514 definitely seem to be very relevant to my current problem.

I will check out shortly with the Basis guys and get the necessary profile added.

If that doesnt work, I guess I will try out note 329961.

Anyway, thanks a to for your insightful answer.

Regards

Pradyut

[Former Member · Accepted solution]

Dear Paolo,

I can not log on to R/3 as ALEREMOTE. It is a background user and I am only allowed to logon using a dialog user.

Anyway, to be on the safer side I will get the profile P_BAS_ALL added to the ALEREMOTE user. Will check the load once that is done.

Thanks anyway for your reply.

Regards

Pradyut

[Former Member · Accepted solution]

Dear Anil,

Thanks a lot for your help. It indeed worked and after the addition of the profile P_BAS_ALL , the load is now working absolutely fine now.

Thanks also to Paolo for his valuable suggestions and tips.

My problem is now resolved!

Regards

Pradyut.

[Former Member · Accepted solution]

Is there a way of accomodating both INPERIOD and FORPERIOD at same in the cube?