on 07-13-2010 3:43 AM
Hi friends
I have one requirement i have field called Product line under two different nodes ( Document node & Parts node).
I need to map Product line from these two nodes to same target field ( Product_descr).
KIndly guide how to map these fields from two nodes to same taget.
regards,
Renu
Hi Renu,
The best thing would be right click on PRODUCTLINE_DESCR and duplicate it. Now you have two PRODUCTLINE_DESCR nodes. For the first one map from Product line from Document node and for the second PRODUCTLINE_DESCR map the Product line from Parts node. So if you dont have one the other one will be there in target. If you both then you will have both of them in your target and if you dont have any Product line in source you dont have any target.
Regards,
---Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Renu,
Condition -1:
If the target node occurance you need to check, if the target node (Product_descr) occurance is more than one (like 0..unbound or 1..unbound or 0..N or 1..N) then you can simply repeat the node (select that node and right click and repeat select) then map
Document_node-ProductLine to First node of Product_descr-ProductLine
Parts_node-ProductLine to second(duplicated) node of Product_descr-ProductLine
Condition-2:
If the target node occurance is 0..1 or 1..1 then based on the condition we need to map the field.
Here first we need to check the Document_node-ProductLine exists or not if it is exists then map this field to target field, if Document_node-ProductLine not exists then we need to check Parts_node-ProductLine and map this field.
Regards
Ramesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
it depends on if you can do it or not.
1. Is the target field (or its parent node) has an occurrence of greater than 1?
if so, easily duplicate the node (right click and duplicate) and then achieve your mapping
2. If the occurrence is 1-1, then you will need to have a condition to map the field. here also duplicate and apply the condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear friends,
My target fileld node ( Product _description) s o..unbounded.When i duplicate it is not coming .I have not dulpicate its parent node.
For your reference target payload
<?xml version="1.0" encoding="UTF-8"?>
<ns1:MT_AL4ECC_PROXY xmlns:ns1="http://palm.com/AL4ECC"><AGILE_DATA><FILENAME>ECO191672009-09-25T23:21:38Z</FILENAME><CHANGE_ORDER><CHANGE_NUM>19167</CHANGE_NUM><CHANGE_TYPE>ECO</CHANGE_TYPE><DESC>Add SKU setup information to 3464NA-SPR and 3452WW-SPR</DESC><VALID_FROM>20090925232138</VALID_FROM><CHGNUM_STATUS>01</CHGNUM_STATUS></CHANGE_ORDER><MATERIAL><MAT_NUM>3452WW-SPR</MAT_NUM><MAT_TYPE>FGI</MAT_TYPE><MAT_GRP>0410 Top Assembly Accessory</MAT_GRP><PROD_HEIR>481862870521646094</PROD_HEIR><PRODUCTLINE_DESCR><VALUE>PIXIE</VALUE></PRODUCTLINE_DESCR><MAT_DESC>SKU, TOUCSTONE BACK COVER, PIXIE, SPRINT</MAT_DESC><OLD_REV>0</OLD_REV><NEW_REV>1</NEW_REV><EAN_CAT>PM Internal Assignment - Palm Inc. UPC</EAN_CAT><EAN_CODE></EAN_CODE><UPC_CODE>805931057310</UPC_CODE><INSP_TXT></INSP_TXT><PLNT_SALESORG><VALUE>1080-1000</VALUE></PLNT_SALESORG><PURCHASE_GRP>999 ODM</PURCHASE_GRP><SP_PROC_TYPE></SP_PROC_TYPE><WWEIGHT>0.017</WWEIGHT><LENGTH_IN>6.1</LENGTH_IN><WIDTH_IN>1.1</WIDTH_IN><HEIGHT_IN>3.3</HEIGHT_IN><LENGTH_CM>15.5</LENGTH_CM><WIDTH_CM>2.8</WIDTH_CM><HEIGHT_CM>8.3</HEIGHT_CM><GROSS_WT_LBS>0.14</GROSS_WT_LBS><NET_WT_LBS>0.14</NET_WT_LBS><GROSS_WT_KG>0.062</GROSS_WT_KG><NET_WT_KG>0.062</NET_WT_KG><D_CHAIN_STATUS>Prototype</D_CHAIN_STATUS><VALID_FROM>20090925</VALID_FROM></MATERIAL><AML></AML></AGILE_DATA></ns1:MT_AL4ECC_PROXY>
My target fileld node ( Product _description) s o..unbounded.When i duplicate it is not coming .I have not dulpicate its parent node.
If the target node PRODUCTLINE_DESCR is 0..unbounded then you dont need to repeat the parent node (unless some other logic is required)
Can you give example of repeatition of the PRODUCTLINE_DESCR node, it may help to provide you with proper solution.
Once you have duplicated the target node then you should map the individual node with the corresponding source node.
Also I could see a field VALUE inside PRODUCTLINE_DESCR, map it accordingly!
Regards,
Abhishek.
Dear friends,
My source payload structure
<?xml version="1.0" encoding="UTF-8"?>
<ns0:AgileData ns2:schemaLocation="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns0="http://support.agile.com/misc/axml/2008/05/" xmlns:ns2="http://www.w3.org/2001/XMLSchema-instance">
<ns0:ChangeOrders uniqueId="">
<ns0:CoverPage>
<ns0:Number/>
<ns0:Status/>
<ns0:ChangeType/>
<ns0:ChangeCategory/>
<ns0:DescriptionOfChange/>
<ns0:ReasonForChange/>
<ns0:ReasonCode/>
<ns0:Workflow/>
<ns0:ChangeAnalyst/>
<ns0:Originator/>
<ns0:DateOriginated/>
<ns0:DateReleased/>
<ns0:ProductLines>
<ns0:Value>CASTLE</ns0:Value>
</ns0:ProductLines>
</ns0:CoverPage>
<ns0:AffectedItems referentId="">
<ns0:ItemNumber/>
<ns0:ItemDescription/>
<ns0:NewRev/>
<ns0:LifecyclePhase/>
<ns0:EffectiveDate/>
<ns0:ObsoleteDate/>
<ns0:OnOrder/>
<ns0:Stock/>
<ns0:WorkInProgress/>
<ns0:FinishedGoods/>
<ns0:Field/>
<ns0:Redlines/>
</ns0:AffectedItems>
<ns0:AffectedItems referentId="">
<ns0:ItemNumber/>
<ns0:ItemDescription/>
<ns0:OldRev/>
<ns0:NewRev/>
<ns0:OldLifecyclePhase/>
<ns0:LifecyclePhase/>
<ns0:EffectiveDate/>
<ns0:ObsoleteDate/>
<ns0:OnOrder/>
<ns0:Stock/>
<ns0:WorkInProgress/>
<ns0:FinishedGoods/>
<ns0:Field/>
<ns0:Redlines>
<ns0:RedlinedBOMRow RedlineAction="Unchanged">
<ns0:RedlinedBOMRowCurrent>
<ns0:AttachmentsImage>false</ns0:AttachmentsImage>
<ns0:ManufacturerImage>false</ns0:ManufacturerImage>
<ns0:PendingChangesImage>false</ns0:PendingChangesImage>
<ns0:HasBeenRedlinedImage>false</ns0:HasBeenRedlinedImage>
<ns0:ItemNumber>760-10066-14</ns0:ItemNumber>
<ns0:ItemDescription>SUB ASSY, SOFTWARE, PALM100HK PRE, SPRINT, PRL 60659, WEBOS 1.4.0</ns0:ItemDescription>
<ns0:ItemRev>OB</ns0:ItemRev>
<ns0:Qty>1</ns0:Qty>
<ns0:FindNum>1</ns0:FindNum>
<ns0:ReferenceDesignators/>
</ns0:RedlinedBOMRowCurrent>
</ns0:RedlinedBOMRow>
<ns0:RedlinedBOMRow RedlineAction="Unchanged">
<ns0:RedlinedBOMRowCurrent>
<ns0:AttachmentsImage>false</ns0:AttachmentsImage>
<ns0:ManufacturerImage>true</ns0:ManufacturerImage>
<ns0:PendingChangesImage>false</ns0:PendingChangesImage>
<ns0:HasBeenRedlinedImage>false</ns0:HasBeenRedlinedImage>
<ns0:ItemNumber>170-10494-00</ns0:ItemNumber>
<ns0:ItemDescription>SUB ASSY, UPPER PRE</ns0:ItemDescription>
<ns0:ItemRev>E</ns0:ItemRev>
<ns0:Qty>1</ns0:Qty>
<ns0:FindNum>2</ns0:FindNum>
<ns0:ReferenceDesignators/>
</ns0:RedlinedBOMRowCurrent>
</ns0:RedlinedBOMRow>
<ns0:RedlinedBOMRow RedlineAction="Unchanged">
<ns0:RedlinedBOMRowCurrent>
<ns0:AttachmentsImage>false</ns0:AttachmentsImage>
<ns0:ManufacturerImage>true</ns0:ManufacturerImage>
<ns0:PendingChangesImage>false</ns0:PendingChangesImage>
<ns0:HasBeenRedlinedImage>false</ns0:HasBeenRedlinedImage>
<ns0:ItemNumber>170-10495-00</ns0:ItemNumber>
<ns0:ItemDescription>SUB ASSY, LOWER, EVDO, PRE</ns0:ItemDescription>
<ns0:ItemRev>L1</ns0:ItemRev>
<ns0:Qty>1</ns0:Qty>
<ns0:FindNum>3</ns0:FindNum>
<ns0:ReferenceDesignators/>
</ns0:RedlinedBOMRowCurrent>
</ns0:RedlinedBOMRow>
<ns0:RedlinedBOMRow RedlineAction="Unchanged">
<ns0:RedlinedBOMRowCurrent>
<ns0:AttachmentsImage>false</ns0:AttachmentsImage>
<ns0:ManufacturerImage>true</ns0:ManufacturerImage>
<ns0:PendingChangesImage>false</ns0:PendingChangesImage>
<ns0:HasBeenRedlinedImage>false</ns0:HasBeenRedlinedImage>
<ns0:ItemNumber>153-10795-00</ns0:ItemNumber>
<ns0:ItemDescription>FILM, PROTECTION, HOUSING A, PRE</ns0:ItemDescription>
<ns0:ItemRev>A</ns0:ItemRev>
<ns0:Qty>1</ns0:Qty>
<ns0:FindNum>4</ns0:FindNum>
<ns0:ReferenceDesignators/>
</ns0:RedlinedBOMRowCurrent>
</ns0:RedlinedBOMRow>
<ns0:RedlinedBOMRow RedlineAction="Unchanged">
<ns0:RedlinedBOMRowCurrent>
<ns0:AttachmentsImage>true</ns0:AttachmentsImage>
<ns0:ManufacturerImage>false</ns0:ManufacturerImage>
<ns0:PendingChangesImage>false</ns0:PendingChangesImage>
<ns0:HasBeenRedlinedImage>false</ns0:HasBeenRedlinedImage>
<ns0:ItemNumber>180-10642-XX</ns0:ItemNumber>
<ns0:ItemDescription>DWG, FNL ASSY, HANDSET, PRE, EVDO & SPRINT</ns0:ItemDescription>
<ns0:ItemRev>A</ns0:ItemRev>
<ns0:Qty>0</ns0:Qty>
<ns0:FindNum>9990</ns0:FindNum>
<ns0:ReferenceDesignators/>
</ns0:RedlinedBOMRowCurrent>
</ns0:RedlinedBOMRow>
<ns0:RedlinedBOMRow RedlineAction="Unchanged">
<ns0:RedlinedBOMRowCurrent>
<ns0:AttachmentsImage>true</ns0:AttachmentsImage>
<ns0:ManufacturerImage>false</ns0:ManufacturerImage>
<ns0:PendingChangesImage>false</ns0:PendingChangesImage>
<ns0:HasBeenRedlinedImage>false</ns0:HasBeenRedlinedImage>
<ns0:ItemNumber>800-12104-00</ns0:ItemNumber>
<ns0:ItemDescription>REF DOC, INSPECTION,KEY INTERFACE GAPS, PRE</ns0:ItemDescription>
<ns0:ItemRev>E</ns0:ItemRev>
<ns0:Qty>0</ns0:Qty>
<ns0:FindNum>9991</ns0:FindNum>
<ns0:ReferenceDesignators/>
</ns0:RedlinedBOMRowCurrent>
</ns0:RedlinedBOMRow>
</ns0:Redlines>
</ns0:AffectedItems>
<ns0:PageThree/>
<ns0:PageTwo>
<ns0:CreateUser/>
</ns0:PageTwo>
</ns0:ChangeOrders>
<ns0:Documents uniqueId="">
<ns0:TitleBlock>
<ns0:Number/>
<ns0:DocumentType/>
<ns0:LifecyclePhase/>
<ns0:Description/>
<ns0:DocumentCategory/>
<ns0:ProductLines>
<ns0:Value>CASTLE</ns0:Value>
</ns0:ProductLines>
<ns0:Rev/>
<ns0:RevReleaseDate/>
</ns0:TitleBlock>
<ns0:PageTwo>
<ns0:CreateUser>Joann Nunes (jnunes)</ns0:CreateUser>
</ns0:PageTwo>
</ns0:Documents>
<ns0:Parts uniqueId="">
<ns0:TitleBlock>
<ns0:Number/>
<ns0:PartType/>
<ns0:LifecyclePhase/>
<ns0:Description/>
<ns0:PartCategory/>
<ns0:Size/>
<ns0:ProductLines>
<ns0:Value>CASTLE</ns0:Value>
</ns0:ProductLines>
<ns0:Rev/>
<ns0:RevReleaseDate/>
<ns0:EffectivityDate/>
</ns0:TitleBlock>
<ns0:PageTwo>
<ns0:List12/>
<ns0:List24/>
<ns0:CreateUser/>
</ns0:PageTwo>
</ns0:Parts>
</ns0:AgileData>
Hi Abhishek,
It is a complex mapping interface. I will try to expaing explain as per my understanding:
From Source:
In the source payload there are 3 nodes Affected items, Documents ,Parts,
In the targert based on number of afffected items ---> materials node will be created.
In the Node 'Documents' there is sub node called Title Block underneath the node we have node calle "Product Line" (0....1) in this node i have field called Value ( 0..unbounded).
In the Node 'Parts' there is sub node called Title Block underneath the node we have node called "Product Line"(0....1) in this node i have field called Value.( 0..unbounded).
In the source payload Product line node will come for both the nodes ( Documents & Parts ).
From Target:
The Matrial node will be created in the Target.
Underneath Material Node we have one node called ProductlineDescr_(0..unbounded) and node have field called value.( 0..1)
For eg:
In source if there is two Affected item nodes we will have correspondingly one Documeny node and one Parts node for those 2 affected items in source
Hence we will have 4 materials node get created in target.
Under each matarial node the Product Line node ( Field - VALUE ) will data.
Now Producltine node from Documents and parts node need to be mapped to Target node ( Productline_Descr).
This is my requirement.
if you give mapping fiugure rather than description i can understand easily.
Renu.
I need to map Product line from these two nodes to same target field ( Product_descr).
Assuming that there is no condition involved.
Duplicate the target node (or its parent node) if the max occurence is more than 1 and then map the two target nodes individually to the two different source nodes.
Regards,
Abhishek.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there any specific condition provided?
1. Like Document node or part node exists or not null map it to target product desc.
2. select both fields from source and do concatenate,
You can map to target depends on ur condition.
Regards
Ramg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.