Error in delta

Hello All.
I have run a delta load from an ODS to a CUBE without PSA. Now I need to rerun that delta.
How can I do it?
Thanks all.

Hi,
Make sure that you delete the data mart status from ODS before you do the delta load from ODS to Cube for the old request.
1. Dleet the red request from the cube.
2. Go to Manage of the ODS.
3. CLick on data mart status of the ODS request.
4. Click on Trash icon on the enxt screen.
5. refresh the Manage screen of the ODS.
6. now try doing delta load again.
Before deleteing the data mart status make sure the request id of the Data mart status ad the red status request in the cube is same.
Regards,
Rohini

Similar Messages

Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

hi all,
i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
not able to figure out the actual issue and how to solve it.
can anyone suggest?
below is the details of the short dump
Short text
    Exception condition "UNKNOWN_TRANSCAT" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
     exception
    condition "UNKNOWN_TRANSCAT".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "RAISE_EXCEPTION" " "
    "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
    "SORT_TRANSACTIONS"
    or
    "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
    or
    "SBIE0001 " "UNKNOWN_TRANSCAT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

Hi,
It seems like some routine are there and check your rotines , transformation etc.
Regards
sivaraju

Error in delta run in the process chain

Hello Experts,
I have a delta infopackge that runs everyday , since many days the process chain is giving error at the IP.
The IP is red everyday and the following objects does not start, however when I check in the monitor the ip is completed successfully without any errors.
I checked the logs which is in greeen in the batch job , please find the details below.
Job started
Step 001 started (program RSPROCESS, variant &0000000111903, user ID ALEREMOTE)
Last delta upload not yet completed. Cancel
Data saved successfully
Start InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7
Last delta upload not yet completed. Cancel
Last delta upload not yet completed. Cancel
InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7 created request
Request REQU_4L001XOSR2IQQ14M90QLO1CTA could not be generated with InfoPackage REQU_4L001XOSR2IQQ14M90QLO1CTA without errors
Last delta upload not yet completed. Cancel
Error After Starting InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7 in Process Chain ZIM_INT_ORDER
Entire chain now has status 'A'
Job finished
Could you please suggest.

Hello
Thanks for your reply
the problem was with the way it was schudled, the chian was ticket at periodic run , as a result it as running automatically, and causing problem.
I have removed the periodic n saved it again ...the error stopped appearing !
The issue is resolved now.
Thanks for your help.

Error in Delta request. can any one help me

Hi Guys
When i ran a delta from R3
i am getting the error :Time out during allocate/CPIC call THE SAPCMINIT'#'TIMEOUTCONNECTtion
But the Init was perfect.
When i want to Execute the LUW manually at SM58 in source system. I dont see the any entry there.
Please help me in this regard
Regards
KA
Message was edited by: A K

Hi Guys
When i ran a delta from R3
i am getting the error :Time out during allocate/CPIC call THE SAPCMINIT'#'TIMEOUTCONNECTtion
But the Init was perfect.
When i want to Execute the LUW manually at SM58 in source system. I dont see the any entry there.
Please help me in this regard
Regards
KA
Message was edited by: A K

Error in delta load activation

Hello every one,
we have generated generic data source and assigned delta on Shipment number with lower limit 10.
when we loaded data through initial load it got all the records from R3 and scheduled delta (suppose to get 0 records because no data was generated ), Delta is bringing 6 records with it and getting error while activating in ODS due to duplicates.
1.How these 6 record came from with out generating data in R3..
2.while activating it is showing error by saying below message
>System error occurred (RFC call)
>Key value exists in duplicate (Not allowed by the ODS object type)
>Activation of data records from ODS object ZODSNAME terminated
>No confirmation for request ODSR_4APQX0IG5LKYJX8248G9QB314 when activating the ODS object ZODSNAME
>Request REQU_4APPPJ630P70EWTMMY686TTSO , data package 000001 incorrect with status 5
>Request REQU_4APPPJ630P70EWTMMY686TTSO , data package 000001 not correct
>Inserted records 1- ; Changed records 1- ; Deleted records 1-
If i am not clear ..please ask i am ready to give required inputs
Please through some light so solve this issue and to load delta properly with out error.
Thanks in Advance
Sandy

Hello Praveen,
Appreciate for your reply....
we created the Data source from View
and the activated the Delta with Numeric pointer where the lower limit was 10 and the upper limit was empty
Then replicated and started loading init first and delta next.
correct me if i am wrong.
Thanks
Sandy

Error in delta load activation in ODS

Hello every one,
we have generated generic data source and assigned delta on Shipment number with lower limit 10.
when we loaded data through initial load it got all the records from R3 and scheduled delta (suppose to get 0 records because no data was generated ), Delta is bringing 6 records with it and getting error while activating in ODS due to duplicates.
1.How these 6 record came from with out generating data in R3..
2.while activating it is showing error by saying below message
System error occurred (RFC call)
Key value exists in duplicate (Not allowed by the ODS object type)
Activation of data records from ODS object ZODSNAME terminated
No confirmation for request ODSR_4APQX0IG5LKYJX8248G9QB314 when activating the ODS object ZODSNAME
Request REQU_4APPPJ630P70EWTMMY686TTSO , data package 000001 incorrect with status 5
Request REQU_4APPPJ630P70EWTMMY686TTSO , data package 000001 not correct
Inserted records 1- ; Changed records 1- ; Deleted records 1-
If i am not clear ..please ask i am ready to give required inputs
Please through some light so solve this issue and to load delta properly with out error.
Thanks in Advance
Sandy

Hello,
1. The records may be due to Safety delta interval you have maintained in your generic datasource. In RSA7, you can check STAT column for your data source. Click on the Pointer for Generic delta. you would see Shipment Number from which next delta would be pulled it.
2. Have you unchecked "Do Not Check Uniqueness of Data" in your DSO. This may be the cause for activation failure as same records are coming in as per the safety interval maintained.

Error in delta load (Urgent)

hello gurus,
i had loaded a delta form inventory(2lis_03_bf) where it got error while loading to 2 data targets,
then i made the traffic singles to red in the monitor screen to do a repeat .
where after doing ,i got problem ..I'M not able to go and start the repeat in InfoPackage
if i try to do the schedule, screen is taken to ABAP run time error.
Plz help ME in high priority
Points are alloted

Delete all the requests from the cube for which the data was not loaded . Try reloading.
Next time, when you get into such problems, instead of mamking the requests to red, just wait for a few minutes for the job to finish and then try to diagnose the problems and you can fix it once and for all.
Ravi Thothadri

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

Error in delta extraction with SAP DataSource 2LIS_11_VAHDR ...

Hi all
I used the old data load process(3.5) in 2004s system.
There are errors in detla extraction with SAP data source
2LIS_11_VAHDR
2LIS_11_VAITM
2LIS_12_VCHDR
2LIS_12_VCITM
The delta data(before/after image) aren't right.
Has anyone experices with this problem?
thanks in advance

No Problems yet,explain the error message with error number in details here for some one to help you.
Hope it Helps
Chetan
@CP..

Data load error in Delta mode

Hi,
I have a DSO as an infoprovider and in a process chain I am loading data in delta mode into it and then transforming it in the next step into an infocube.
Everything was ok until I got an error in request id 1571 and process chain is finished with error. After this request I have request ids 1624, 1682, 1802 and 1854. The QM status and Technical status for these four requests are ok. I spot an invalid character is source of error. How should I fix it in PSA? As you know for editting data into PSA I have to delete it from target infoprovider and I don't want to do this. Is there any other solution to fix a invalid character in this situation?
By the way, is it possible to attach a screenshot of error to message in sdn forums?
Regards,

What is the source for this DSO from which you are loading deltas?
If the request number 1571 is the latest in the DSo you can just directly delete the request 1571 and edit the data in PSA.
If not if you have the rest of the 4 request on the top of the request 1571 and they are activated then you need to delete the complete 5 request and reload them all.
If the top 4 requests are not activated you can delete the single request 1571 and edit the data and proceed further.
To attach the screen shot directly not possible, just upload the error screen shot in the private URL and paste that URL .
Edited by: prashanthk on Nov 15, 2010 11:49 AM

Error in Delta Infopacakge after successful initialization

Hi,
We are having a content datasource 0customer_attr for which we are having Init and Delta infopackages. After the BI system copy from Productive system to Quality system, we have re-connected the R/3 source system and deleted the old Init settings and cleared the PSA. After which we ran the program RSSM_OLTP_INIT_DELTA_UPDATE for that datasource and started the Initialize with/without data transfer which ran successfully. But whenever we try to run the delta infopackage, it is giving the following error :
Error message from the source system
Diagnosis
An error occurred in the source system. (Job terminated in source system --> Request set to red)
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
For the first time when we tried with delta it gave a different type of message like :
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
PLEASE ADVISE----
--Akashdeep

Hi,
Chk the extractor job in sourcesystem whether it is canceld/successful....
The job starts with BIREQU_*
Or go via monitor>environment>job overview-->in the sourcesystem and chk the status there....
rgds,
Edited by: Krishna Rao on Nov 25, 2009 6:28 PM

Error while Delta initializing for COPA

Hi All,
I got error "SYSTEM_IMODE_TOO_LARGE" trough ST22
While delta initializing for COPA. this error come after I create Start Routine" on Cube, just for info the routine for convert row to column.
But if I remove the routine the Initializing is OK.
Can you please suggest a solution for this ?
regards,
here my routine:
data: wa_datapackage like DATA_PACKAGE occurs 0 with header line.
data: bulan(6) type c.
data: REV000 like DATA_PACKAGE-/BIC/ZCPCOPAVL,
        NETSLS like DATA_PACKAGE-/BIC/ZCPCOPAVL,
        COGS like DATA_PACKAGE-/BIC/ZCPCOPAVL,
        GRSPFT like DATA_PACKAGE-/BIC/ZCPCOPAVL,
        OPSICM like DATA_PACKAGE-/BIC/ZCPCOPAVL,
        PFTALHO like DATA_PACKAGE-/BIC/ZCPCOPAVL,
        PFTALC like DATA_PACKAGE-/BIC/ZCPCOPAVL,
        GRSICM like DATA_PACKAGE-/BIC/ZCPCOPAVL.
wa_datapackage[] = DATA_PACKAGE[].
refresh DATA_PACKAGE.
FREE DATA_PACKAGE.
loop at wa_datapackage.
    DATA_PACKAGE = wa_datapackage.
*AERLOS     Revenue SD
    DATA_PACKAGE-/BIC/ZCPCOPAIT = 'AERLOS'.
    DATA_PACKAGE-/BIC/ZCPCOPAVL = DATA_PACKAGE-G_AERLOS.
    Append DATA_PACKAGE.
*AVV120     Disc Prinsipal
    DATA_PACKAGE-/BIC/ZCPCOPAIT = 'AVV120'.
    DATA_PACKAGE-/BIC/ZCPCOPAVL = DATA_PACKAGE-G_AVV120.
    Append DATA_PACKAGE.
*AVV121     Disc TRS Regular
    DATA_PACKAGE-/BIC/ZCPCOPAIT = 'AVV121'.
    DATA_PACKAGE-/BIC/ZCPCOPAVL = DATA_PACKAGE-G_AVV121.
    Append DATA_PACKAGE.
*AVV122     Disc TRS Other
    DATA_PACKAGE-/BIC/ZCPCOPAIT = 'AVV122'.
    DATA_PACKAGE-/BIC/ZCPCOPAVL = DATA_PACKAGE-G_AVV122.
    Append DATA_PACKAGE.
*AVV123     Cash Discount
    DATA_PACKAGE-/BIC/ZCPCOPAIT = 'AVV123'.
    DATA_PACKAGE-/BIC/ZCPCOPAVL = DATA_PACKAGE-G_AVV123.
    Append DATA_PACKAGE.
endloop.

Hi All,
As info in my machine the package size is 20000,
Max line 100000, frequency 10 and max proc 3, I check this through SBIW-General Setting-Maintain Control.
Is this what u mean Roberto? (CMIIW)
And total record transfer from COPA is 312633.
Here there result of ST22,
Roll area...................... 2722448
Extended memory (EM)........... 582160704
Assigned memory (HEAP)......... 1999599904
Short area..................... 0
Paging area.................... 24576
Maximum address space.......... 4294967295
I agreed with u Mosser about that and my cube is OK with create all key figure that I need. But this cube can't support for another report.
Thanks
supriatna

Error on delta load 2LIS_04_MATNR CALL_FUNCTION_NOT_FOUND

Hello Everyone,
When trying to load delta from 2LIS_04_MATNR i get the below error message.
Please any suggestions on how to fix this?
Function module "/BI0/QI2LIS_04_PEMATNR0002" not found.
The function module "/BI0/QI2LIS_04_PEMATNR0002" was called, but cannot be
found in the Function Library.
The current ABAP/4 program "SAPMSSY1 " had to
one of the statements could not be executed.
If you have access to the note system yourself, use the following
search criteria:
"CALL_FUNCTION_NOT_FOUND"
"SAPMSSY1 " or "SAPMSSY1 "
"XAB_RUN_DRIVER"
Function modules with names similar to "/BI0/QI2LIS_04_PEMATNR0002":
/BI0/QI2LIS_04_PEMATNR0001
/BI0/QI2LIS_04_PEMATNR
/BI0/QI2LIS_04_PECOMP0001
/BI0/QI2LIS_04_PECOMP
/BI0/QI2LIS_03_BF0002
/BI0/QI2LIS_02_CGR0001
/BI0/QI2LIS_02_HDR0001
/BI0/QI2LIS_02_SCL0004
/BI0/QI2LIS_02_SGR0001
/BI0/QI2LIS_02_SCL0002
The termination occurred in the ABAP/4 program "SAPMSSY1 " in
"XAB_RUN_DRIVER".
The main program was "RSFHGEN2 ".
The termination occurred in line 232
of the source code of program "SAPMSSY1 " (when calling the editor 2320).

Hi,
did it ever work? Does it work with a full upload? Did you transport it and does it work in a other system but not in the transported system? What Version are we talking about? Did you activate it from Business Content?
br
Joerg

Getting invalid-attribute-value Error during Delta Import on Call-based ECMA2

I'm developing an ECMA2 MA to which supports delta imports. I have found very few samples of working code to do delta imports, so my attempts are created
using a lot of trial and error... Any samples of working Call based MA's with delta support would be much appreciated :-)
The data is located in a SQL server and the schema (for delta) is like this (simplified):
EmpID string
Status string
UPDATESTATUS string (<-- This is the update column with values New/Update/Delete)
For each EmpID, there may be multiple Status values, i.e. Status should be imported into a multi value attribute in FIM.
For the full import this is working as expected, but I run into issues when attempting to do the delta imports
The code for the delta import
private
GetImportEntriesResults GetImportEntries_Delta(GetImportEntriesRunStep importRunStep)
GetImportEntriesResults importReturnInfo;
List<CSEntryChange> csentries =
new List<CSEntryChange>();
string employeeID =
null;
string appStatus =
null;
string currEmployeeID =
CSEntryChange csentry =
null;
List<string> appStatusList =
new List<string>();
string changeMode =
for (int i = currentReadRecord; i <= da.Tables["AppStatus"].Rows.Count - 1; i++)
if (currEmployeeID != da.Tables["AppStatus"].Rows[i].ItemArray.GetValue(0).ToString().Trim())
if (currEmployeeID !=
"") // this should be true except for the first run
csentry.AttributeChanges.Add(AttributeChange.CreateAttributeUpdate("IdentityStores", appStatusList));
csentries.Add(csentry);
appStatusList = new
List<string>();
if (csentries.Count >= m_importPageSize)
 currentReadRecord = i;
importReturnInfo = new
GetImportEntriesResults();
importReturnInfo.MoreToImport = (i <= da.Tables["AppStatus"].Rows.Count - 1);
importReturnInfo.CSEntries = csentries;
return importReturnInfo;
changeMode = da.Tables["AppStatus"].Rows[i].ItemArray.GetValue(2).ToString().Trim();
csentry = CSEntryChange.Create();
csentry.ObjectType = "ApplicationIdentity";
employeeID = da.Tables["AppStatus"].Rows[i].ItemArray.GetValue(0).ToString().Trim();
currEmployeeID = (string)employeeID;
switch (changeMode)
case "New":
csentry.ObjectModificationType = ObjectModificationType.Add;
csentry.AttributeChanges.Add(AttributeChange.CreateAttributeAdd("EmployeeID", employeeID));
break;
case "Update":
csentry.ObjectModificationType = ObjectModificationType.Update;
csentry.DN = employeeID;
break;
case "Delete":
csentry.ObjectModificationType = ObjectModificationType.Delete;
 csentry.DN = employeeID;
break;
default:
throw new
UnexpectedDataException(string.Format("Unknown modification type: {0}", changeMode));
appStatus = da.Tables["AppStatus"].Rows[i].ItemArray.GetValue(1).ToString().Trim();
appStatusList.Add(appStatus);
// save the last object
if (csentry != null)
csentry.AttributeChanges.Add(AttributeChange.CreateAttributeUpdate("IdentityStores", appStatusList));
csentries.Add(csentry);
importReturnInfo = new
GetImportEntriesResults();
importReturnInfo.MoreToImport = false;
importReturnInfo.CSEntries = csentries;
return importReturnInfo;
The code compiles and executes, but the delta import fails with the "invalid-attribute-value" message per csentry.
From the eventlog I have the following message
The server encountered an unexpected error while performing an operation for a management agent.
"System.InvalidCastException: Unable to cast object of type 'System.Collections.Generic.List`1[System.String]' to type 'System.String'.
 at Microsoft.MetadirectoryServices.Impl.Ecma2ConversionServices.AddAttributeToDImage(CDImage* pdimage, String attributeName, AttributeModificationType
attributeModificationType, IList`1 attributeValueChanges, Int32 escapeReferenceDNValues)
 at Microsoft.MetadirectoryServices.Impl.Ecma2ConversionServices.ConvertToDImage(CSEntryChange csEntryChange, CDImage** ppDImage, Int32 escapeReferenceDNValues)
 at Microsoft.MetadirectoryServices.Impl.ScriptHost.InvokeExtMA_ImportEntry(UInt32 cBatchSize, UInt16* pcszCustomData, UInt32 cFullObject,
_OCTET* rgoctFullObject, UInt32* rgomodt, UInt32* pcpcszChangedAttributes, UInt16*** prgpcszChangedAttributes, Int32 fIsDNStyleNone, UInt16** ppszUpdatedCustomData, _OCTET* rgoctCSImage, Int32* rgextec, UInt16** rgpszErrorName, UInt16** rgpszErrorDetail, Int32*
pfMoreToImport)"
To me it seems as if FIM is unable to process the List of strings that is returned when processing the delta. Remember that this works OK when doing the full import.
Do you have any suggestions as to why this fails?
Kjetil

Hi,
Thank you Søren! I got some good clues for the right direction from your answer. If anyone would be looking same answers the correct solution would be down below. I hope it would be help for someone else too.
Get-Shema.ps1
$obj
= New-Object
-Type PSCustomObject
$obj
| Add-Member
-Type NoteProperty
-Name "Anchor-Id|String"
-Value 1
$obj
| Add-Member
-Type NoteProperty
-Name "objectClass|String"
-Value "user"
$Obj
| Add-Member
-Type NoteProperty
-Name "IsLicensed|Boolean"
-Value $true
$Obj
| Add-Member
-Type NoteProperty
-Name "FirstName|String"
-Value ""
$Obj
| Add-Member
-Type NoteProperty
-Name "LastName|String"
-Value ""
$Obj
| Add-Member
-Type NoteProperty
-Name "mail|String"
-Value ""
$Obj
| Add-Member
-Type NoteProperty
-Name "immutableId|String"
-Value ""
$Obj
| Add-Member
-Type NoteProperty
-Name "DisplayName|String"
-Value ""
$Obj
| Add-Member
-Type NoteProperty
-Name "UsageLocation|String"
-Value ""
$Obj
| Add-Member
-Type NoteProperty
-Name "ProxyAddresses|String[]"
-Value ("","")
$Obj
| Add-Member
-Type NoteProperty
-Name "Licenses|String[]"
-Value ("","")
$obj
Import.ps1
#Always pass objects as hash table in pipeline
foreach ($User
in $Users)
$obj = @{}
$obj.Add("Id",
$User.UserPrincipalName)
$obj.Add("objectClass",
"user")
$obj.Add("IsLicensed",
$User.IsLicensed)
$obj.Add("FirstName",
$User.FirstName)
$obj.Add("LastName",
$User.LastName)
$obj.Add("mail",
$User.UserPrincipalName)
$obj.Add("immutableId",
$User.immutableId)
$obj.Add("DisplayName",
$User.DisplayName)
$obj.Add("UsageLocation",
$User.UsageLocation)
$obj.Add("ProxyAddresses", ($User.ProxyAddresses
-ne ""))
$obj.add("Licenses", ($User.Licenses.AccountSkuId))
$obj
Marti

Error in Delta load; error in source system

Hi,
I'm extracting from 0FI_AA_11.
Performed a full load.
Then initialized without data transfer.
When i run delta (0 records) , it fails with 'error in source system' .
Strangely, when I run delta again in REPEAT mode, it runs succesfully.
this is happening everytime i run delta.
Please help

FI_AA_11 is sure capable of handling delta.
It does have some dependencies with master data and these are pretty awkward sometimes.
I don't know when you are running your deltas (during opening hours from the office?) but in your process chain also the MD objects must be present.

Error in delta update

Hi.
I try to create an extractor in R/3 for update delta in an InfoCube.
But BW give me an error :
'Error in Source System'.
I re init the extraction but the error occurs further.
Regards
Angela

You have to do a re-init and then do the data load.
The same problems are discussed in the following link
,"Update mode R is not supported by the extraction API"
Hope this will sovle ur problem.
Regards

Error in delta

Similar Messages

Maybe you are looking for