for the BW Target datastore …
the language : E -English
the codepage :
In DSConfig …
AL_Engine=_.utf-8
We also tried calling from BW. This produced errors when global variables were defined for the Job, but when we changed this to invoke without globals then it worked OK and posted data!
Other way around. The engine should be and the datastore utf-8.
There is no reason to change the engine codepage anymore as it will align itself to the best possible codepage. But the datastores have to match the reality.
this is a bug, this issue is already fixed in 12.2.2.1, there is a Fix Pack for AIX, use that
following is from the release notes
ADAPT01372403:
Data Services was unable to load data into BW Master Transfer Structure and failed with error
message Load data to BW failed: RequestID = <>, Packet Number = <-1>. The issue has been
resolved.
you are using a global variable in your job, and when you try to schedule/execute this job from SAP BW you get an error ? if yes what are the parameters that you are passing to start the job ?
are you able to execute this job from Management Console ?
what is the error you get ?
how is this global variable used in the Job/DF ?
with global varibles what is the error that you are getting ?
how are you starting the Job from BW ? by passing RepoName/JobName ? are you passing the value of global variable as additional args or these variables are initialised in the job
check the JobServer event log file on which the Job is launched, check the command that is used to start the job
since the GV name starts with $, if its not escaped it may cause problem on unix
Thanks, this helped me.
With me it was exactly like that my DS dev is connected to BW dev and BW tst.
BW dev datastore (it is transfer structure) have ending _CD and after transport to tst it had _PA.
So I had to reimport transfer structure and change in data flow _CD one to _PA one.