[InitialLoad] Error Java when executing InitalLoad Job

[Former Member]

Hi all,

I try to setup a job "InitialLoad" to get all the user information from an ABAP WAS.

My problems are :

1st Error : "Exception loading sap_*"

I got this error when all scripts are loaded. (this error is wrapped around warning concerning the license, is something linked ?)

ALL READS passes sound working except for ReadUSER because of "sap_encryptPasswordMD5()"

2nd Error : "runFunctionsInString($FUNCTION.sap_generateDisplayName(/SAPTRX/SAP_AS_ADMIN!!ROLE!!NSP_MiniSAP!!/SAPTRX/SAP_AS_ADMIN)$$) got exception"

I got this error in all WRITE passes

I guess something going wrong with the execution of the job. Can somebody let me know about these issues ?

Thanks,

Benoit

[Former Member]

Here is the error log report,

W:Exception loading sap_generateDisplayName

java.lang.NullPointerException

at com.sap.idm.ic.Config.expandValuesInString(Unknown Source)

at com.sap.idm.ic.DSERunTime.runJob(Unknown Source)

at com.sap.idm.ic.DSERunTime.doCommand(Unknown Source)

at com.sap.idm.ic.DSERunTime.doCommand(Unknown Source)

at com.sap.idm.ic.DSERunTime.run(Unknown Source)

at com.sap.idm.ic.DSERunTime.main(Unknown Source)

Sounds the scripts are not founded ?

Best Regards,

Benoit

[Former Member]

The scripts are not defined in Global Scripts.

Where can I find the sources to import them ?

Thx,

Benoit

[Former Member]

I am having the same issues. There are no scripts in the 'Global scripts' folder.

-

---

Warning Exception loading sap_removeSPMLPrefix

java.lang.NullPointerException

Warning Exception loading sap_generateDisplayName

java.lang.NullPointerException

Warning Exception loading sap_checkSPMLValidDate

java.lang.NullPointerException

Warning Exception loading sap_encryptPassword

java.lang.NullPointerException

Warning Exception loading sap_encryptPasswordMD5

java.lang.NullPointerException

Warning Exception loading sap_initializePassword

java.lang.NullPointerException

-

---

Warning $glb.SAP_MASTER_IDS_ID could not be found!

java.lang.NullPointerException

Warning $glb.SAP_MASTER_IDS_ID could not be found!

java.lang.NullPointerException

-

---

Error runFunctionsInString(PRIV:GROUP:SAP_P1D:$FUNCTION.sap_removeSPMLPrefix(SPML.SAPGROUP.NWDI.Developers)$$) got exception

org.mozilla.javascript.NotAFunctionException: sap_removeSPMLPrefix(SPML.SAPGROUP.NWDI.Developers)

Error runFunctionsInString($FUNCTION.sap_generateDisplayName(NWDI.Developers!!GROUP!!SAP_P1D!!$FUNCTION.sap_removeSPMLPrefix(SPML.SAPGROUP.NWDI.Developers)$$)$$) got exception

org.mozilla.javascript.NotAFunctionException: sap_removeSPMLPrefix(SPML.SAPGROUP.NWDI.Developers)

Error putNextEntry failed storingPRIV:GROUP:SAP_P1D:$FUNCTION.sap_removeSPMLPrefix(SPML.SAPGROUP.NWDI.Developers)$$

Exception from Add operation:java.lang.IllegalArgumentException: No such attribute - entry: PRIV:GROUP:SAP_P1D:$FUNCTION.sap_removeSPMLPrefix(SPML.SAPGROUP.NWDI.Developers)$$

Exception from Modify operation:java.lang.IllegalArgumentException: Entry does not exist - entry: PRIV:GROUP:SAP_P1D:$FUNCTION.sap_removeSPMLPrefix(SPML.SAPGROUP.NWDI.Developers)$$

[Former Member]

We had this problem too once when we first got going in our development environment.

What I had done was import an as abap initial load job without importing the SAP Netweaver Framework. The Framework populates the global scripts, some of which are needed in the jobs - including the script you referenced above.

If you import the SAP Netweaver Framework I believe this should populate your global scripts and solve the issue. As a best practice now, I always do this import first in a new environment.

[Former Member]

>

> We had this problem too once when we first got going in our development environment.
> 
> What I had done was import an as abap initial load job without importing the SAP Netweaver Framework.  The Framework populates the global scripts, some of which are needed in the jobs - including the script you referenced above.
> 
> If you import the SAP Netweaver Framework I believe this should populate your global scripts and solve the issue.  As a best practice now, I always do this import first in a new environment.

That was it! Thank you!