Question:
Hello,
We made a change of the type of field for our datasources from R3. We're using a DB transparent table as datasources and we made a change to a field type from type N to type C. We haven't changed the type of the custom infoobject from N to C that is mapped to this changed type field from R3. We seem to have a problem loading. The load is at the yellow status.
Would you think that this is a problem?? Would we need to change custom infoobject that is receiving the data from the change type field from R3 to be the same to C??
Thnaks
Answer:
Check the dataload monitor, maybe there's a hint to solve the problem (which is there in most cases I guess), but as you said on your own: could be problem with the data types.
Good Luck...
_________________
Juergen Limbach
Answer:
If there is a datatype mismatch definitely the traffic light will not change and data will not get loaded. So ensure that the datatype and the length are the same in the table field as well as the infoobject.
Hello,
We made a change of the type of field for our datasources from R3. We're using a DB transparent table as datasources and we made a change to a field type from type N to type C. We haven't changed the type of the custom infoobject from N to C that is mapped to this changed type field from R3. We seem to have a problem loading. The load is at the yellow status.
Would you think that this is a problem?? Would we need to change custom infoobject that is receiving the data from the change type field from R3 to be the same to C??
Thnaks
Answer:
did u try replicating your datasource under the source system area ?
Answer:
did u try replicating your datasource under the source system area ?
I just tried the replication but I believe the custom R3 datasources that we created from RSO2 need to be transported to test and production systems. Once those are tranported from R3, we would do the replication, but the replication changes the status of the infosources to become deactivated. At least I tested on the 3.0B development system that requires re-activation, and this means that I have to perform transports for the activated versions.
We have a problem that we can't transport because of the upgrade. We still have the test and the production system as 2.0B. while the development system is 3.0B. We suppose that we need to transport the activated version after the replication rather than directly activated from test and production systems.
At this time we are changing our ABAP programs to extract data to Unix flat files and perform uploads.
Would you happen to know if the custom datasources get transported from R3 development system to the test system, perform the replication on the test system, and it would not require the re-activation on 2.0B?? My hands are tied because I am not allowed to transport anything at all now, even from R3.
Thanks