on 03-14-2016 8:43 PM
Hey there!
Pls, I need your help..
I've integrated ECC and EWM systems and sent master data from ECC to EWM through transactions CFM1 and CFM2.
After executing some activities among both systems to confirm it was communicating fine, I created a background job following these steps:
1. deactivate all active versions of IM
2. delete all inactive versions of IM
3. create a new IM for CIF
4. activate the new IM
Afterwards, I've got an error log telling that "BP x already exists" (message R1286).
I tried to delete these BPs and the error logs were "Location x of type 1010 (BSG ZBUSGRP) already exists in APO" (message /SAPAPO/LOM060) and "No mapping entry for x 1010 ZBUSGRP" (message /SAPAPO/LOM007).
So, I'm going from an error to another.
Please, could you help me to solve that?
Best regards.
Dears,
First of all, thanks for your reply. All I did was instructed by an EWM book, but that seems to me it's not sending data updating.
In fact, my big issue is on knowing the best practice to send new master data (i.e. a new BP record on ECC) and its changes (i.e. different address number). What do you suggest?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
which EWM book?
New data - a new model. To be created and activated by job.
Data changes: you keep the model active and have activated BTE for changes.
see here: Data Transfer - Integration via Core Interface (CIF) - SAP Library:
Unfortunately this text describes both possibilities for new and for changed data, but the recommendation in there also should make it clear what to do.
Brgds
Juergen
Juergen,
The book I've been using is "Fundamentals of SCM-EWM", written by two experts. By the way, it's been very helpful..
In your link, I got a new information: the change pointers. I'll have to research about how to do that, guess there is the solution to my issue. I'll keep you posted.
Thank you so far
Ah, that book. Well, this describes to "Activate ALE Change Pointers by Message Type for Automatic Data Transfer in Background" for the message types CIFUS, CIFVEN, and CIFMAT, which you do not do when you activate the change transfer via BTE (which is described two paragraphs before).
Brgds
Juergen
Juergen,
I didn't get the point where change pointers aren't recommended. Instead, everywhere is saying to active it..
If I do what is described on page 181 (excluding 6.2.7 content), that seems to me it's not sending update information, just data load..and that's why it's saying "BP already exists".
What do you suggest to be able to send just new and change information?
Hi,
Here is the sequence for CIF,
1. CFM7 : Deletion of the existing integration model ( check the checkbox Select Inactive IMs Only )
2. CFM1 : Creation of a new integration model
3. CFM3 : Activation of the new integration model
C K Reddy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I think the basic issue you have is that the sequence you do this is wrong.
"1. deactivate all active versions of IM
2. delete all inactive versions of IM
3. create a new IM for CIF
4. activate the new IM"
Why that complicated?
- Create a new IM
- Activate the new IM. Through that the old active version is de-activated
- Delete inactive versions.
As you first de-activated the model and deleted it before creating the new model, the system tries to re-send everything.
Brgds
Juergen
---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.