0RECORDMODE issues for LO applications
I am working the LO extractors for applications 11, 12, and 13. I am also working with DSO's and 1 InfoProvider and a Multiprovider.
I see that the field 0RECORDMODE is a red X that is not mapped to anything. I also see that ROCANCEL is mapped to 0STORNO.
Is it correct to say that if there are changes to an already existing document numbers such as in sales orders or purchase orders; it is strongly recommend to map 0RECORDMODE onto the delivered ROCANCEL field?
But ROCANCEL is already mapped to 0STORNO for the InfoSources that I am working with. What would 0RECORDMODE be mapped to and what would ROCANCEL be mapped to?
It depends on your design.
For ensuring that your delta mechanism works fine, ROCANCEL should be mapped to 0RECORDMODE.
But as you said 0STORNO has a description also as Reversal indicator, i think you should load some test data.
Create some sample data with Key fields as per your ODS definition and then do some changes to this data and load it again and see the values in Change Log table of your ODS.
Change Log table can be seen via ODS
Check here what are values of 0STORNO and 0RECORDMODE (before changing mapping in transfer rules).
But again i suggest ROCANCEL should be mapped to 0RECORDMODE, to make sure your Delta works fine.
Hope it Helps.