This shows you the differences between two versions of the page.
|
bw2:adding_and_updating_business_partner_contacts [2020/12/15 12:25] akoehler created |
bw2:adding_and_updating_business_partner_contacts [2021/02/05 11:21] (current) akoehler |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== Adding and Updating Business Partner Contacts ==== | ==== Adding and Updating Business Partner Contacts ==== | ||
| - | Following is an example for adding a new Business Partner contact. In this example, | + | Following is an example for adding a new Business Partner contact. In this example, the new address's information |
| <code sql> | <code sql> | ||
| Line 14: | Line 14: | ||
| </ | </ | ||
| - | The first part of the query returns the existing contact rows for Business Partner code C99001. | + | The first part of the query returns the existing contact rows for Business Partner code C99001. |
| - | This is another example where the rows also use “Change on value …” for the “Create new record on” option. The value created by “RecordBreak” ensures that records are processed for each combination of address name + address type. | + | This is another example where the rows also use “Change on value …” for the “Create |
| The image below shows the mapping for this process. | The image below shows the mapping for this process. | ||
| - | {{:bw:sapimage12.png?423x123}} | + | {{ :bw:sapimageaddingbp1.png |}} |
| - | {{:bw:sapimage13.png?419x212}} | + | {{ :bw:sapimageaddingbp2.png |}} |
| - | In this case it is not necessary to map CardCode for the rows, since it is mapped at the header (Business Partners) level. | + | In this case, it is not necessary to map CardCode for the rows since it is mapped at the header (Business Partners) level. |