This is what I have for mapping right now. If I map CREATION_DATE to an column in MBBFREP_Customer_Master or MBLGREP_Customer_Xref it works fine. But those two tables have the same key.
Nirogini, Is this a requirement in DMM? Not all files are linked by fields named the same so this seems an odd requirement?
That is the question I have. How do we indicate the join between legacy tables?All I see is a way to indicate the key on legacy tables, but the “key” between T1 & T2 is different than the “key” between T2 & T3.If I set the T3 key field to 3 to match the corresponding field on T2, the transfer to input gives an error because of a key mis-match. If I set the T3 to 1, I get no records because that does not match key 1 on the other tables.Where do we actually indicate how legacy tables are joined?Table 1Table 2Table 3Error
Thanks, I will try our suggestion to see what is happening.I am using a standard IFS transformer so I do not know what it is doing.
heibde, Have you set up one for an Incoming Customer Order (Projection Resource = SalesMessageService.ReceiveCustomerOrder)? If so, do you have an example of how you set up the Routing Address for this?
I found out the issue was the utility creating the file puts double quotes around the fields in the header line - as I would expect since it’s just a csv file.It appears the SYNCDETAILS does not remove the column embrace around the header fields like it does the data fields. I had to manually “correct” the header line and it worked once the double quotes were removed.So we’ve decided not to use SYNCDETAILS and go with the sequencing of fields instead.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
