Update material replication

Hi! I did the material replication in SRM 5.0 with Server 5.5, but I create in R/3 some materials after the replication....
I have to run new material replication process?? or I have another posibility?? I don´t know, a job, etc...??
Thanks
Rose

Hi Rosa,
Look at this thread for explanations on replicating hierarchies:
Switching Backend System
With initial download of DNL_CUST_PROD1, SRM creates 2 new hierarchies:
- R3MATCLASS for material groups/product categoris
- R3PRODHIER for material/service types.
The system assign each of them to purchasing & product applications.
Predefined set types are also assigned in R3PRODHIER.
With next download of DNL_CUST_PROD1, you can update R3MATCLASS, but not R3PRODHIER.
In your case, you would have to delete the existing R3PRODHIER (see how in the thread), but as you have already replicated products (assigned to a material type from this hierarchy), this won't be possible.
So, you must first delete the replicated materials (Hope you didn't use them in some SC...).
Rgds
Christophe
PS: please reward points for helpful answers

Similar Messages

Overwriting Conditions data during Material Replication from R/3 to SRM.

Hi,
 When creating a new info record and then running the material replication program everything looks OK. However, if for the same material you create a new info record or change the existing info record and then run the material replication, some of the previous data is removed.
 We implemented BADI(PRODUCT_CUSTOMER2) to read info records from R/3. When i debug BADI all the info record and condition info is populated. Once the control leaves the BADI standard SAP code is not inserting/updating delta condition records. It is only populating latest info record.
 SRM 4.0
 Support pack level : 11
 BADI Name: PRODUCT_CUSTOMER2
 Method Name: MAP_R3_TO_CRM_MATERIAL
 Conditions Populated in structure : COMT_PROD_SERVICE_BDOC- CONDITIONS-CND_BBP_WORKING_SET.
Thanks in Advance,
Vineela.

Hi
Please go through this ->
Note 715213 Interface change in BAdIs in Release SRM 4.0
Note 689135 Conditions are not downloaded when product is updated in R/3
Note 534899 - Inconsistencies in the Content Workbench
Note 420343 - TIP: Backend price transfer in product conditions
Note 459640 - Category error when transferring backend prices with report
Note 415839 - Removing errors in external product interface
For pricing condition type, go to the SAP Help links
http://help.sap.com/saphelp_srm30/helpdata/en/72/f40f3c98ddaa4ce10000000a11402f/content.htm
and also
http://help.sap.com/saphelp_srm30/helpdata/en/ee/d9df3bbcce4b37e10000000a114084/content.htm
Do you use IPC for pricing? I am not sure whether you can use R/3 4.6C with SRM5.5. Check your systems. Refer SAP notes 539720 if you are using simplified pricing (Classic scenario).
Also check for SAP OSS Notes - 394975 and 420343
Update of price in srm is possible through the SAP OSS Note 420343. This note describes an option to transfer a price from the Backend via a report and a BADI and to store this price in the condition table of the corresponding product in the EBP. But you have to do small changes,i think this note will certainly helps you to transfer material master prices to srm product master automatically.
Update Price in SRM 5.5 Automatically using report - EBP_GET_BACKEND_PRICES
Re: Update Price in SRM 5.5 Automatically using report EBP_GET_BACKEND_PRICES
Condition Type SRM - ECC
Re: Condition Type SRM - ECC
Re: Replicating additional fields (R/3 4.7) to SRM product master
Transfer Inforecord Conditions Scales to SRM Product Master
Hope this will help.
Regards
- Atul

Scheduling updatable materialized view

Hi everybody,
As you may know I have a solution in which I have 5 sites .One master site with 4 updatable materialized view sites.
I want to know that is it correct if I dont set up schedule push to run periodically and set it up to do continuous push ?
I want in at least 2 minutes all sites become update and I have to mention that at first I tried multimaster but our client doesn't want that because they want if one special site becomes unavailable they others can not transfer data to eachother.
I appreciate your help in advance.

Your requirements are a bit unclear...
1) In general, if you are looking to have sites updated within a minute or two of the original transaction being committed, you are better off looking at something like Streams rather than using materialized views.
2) Architecturally, when you set up multi-master replication (which it sounds like you are attempting to do here), you need to choose between synchronous and asynchronous replication. Synchronous replication means that a transaction cannot commit until it has been pushed to all the other nodes, which is great for latency but horrible for performance, scalability, and availability. Very, very few people really want synchronous replication. That leaves asynchronous replication, which would require you to schedule jobs to replicate changes. Some folks who think they want asnychronous replication really want another technology entirely (i.e. DataGuard, RAC, etc).
3) Are you sure about the requirement "they want if one special site becomes unavailable they others can not transfer data to each other"? That says that if one site fails, they want all transactions everywhere to fail. That pretty much defeats the purpose of setting up multi-master replication. If the system is only available as long as every node is available, and you're going to incur the overhead of synchronous replication on every change, you would be far better served consolidating everything into a single data center and potentially using RAC to create a multi-node cluster to spread the work among nodes. There would be very little benefit to offset the complexity of configuring and maintaining a multi-master replication environment if you didn't want the nodes to be able to continue in the event that one of them failed.
Justin

Updatable materialized view

Can someone help with this scenario:
Say I have a master site 1 that has two tables T1A and T1B. I would like to have these tables viewable and updatable on another site 2. Site 1 is on a ship and site 2 is on a shore. Site2 will have access to Site 1 on port 1521.
I have read some on "materialized view" but I'm still not clear how to push the updates made on Site 2 back to Site1.
Can someone provide sample scripts to make replication happens between the two sites?
Thank you.

hi,
try goin thru this online documentation by oracle for details =>
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10732/toc.htm
and for step by step setup of an updatable MV replication =>
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10733/toc.htm

Updatable materialized view- error with CREATE_SNAPSHOT_REPGROUP

I'm trying to create an updatable materialized view from the replication administrators account (REPADMIN). I use the assistant and in the third step (after creating the replication group and the materialized view), when the materialized view is going to be added to the group, I got this error:
ERROR in line 1:
ORA-01403: No data found
ORA-06512: in "SYS.DBMS_REPCAT_SNA_UTL", line 5927
ORA-06512: in "SYS.DBMS_REPCAT_SNA", line 82
ORA-06512: in "SYS.DBMS_REPCAT", line 1332
ORA-06512: in "SYS.DBMS_REPCAT", line 1307
ORA-06512: in line 2
I have also tried to use the command file that the assistant generates (I add below), and the error is triggered within the CREATE_SNAPSHOT_REPOBJECT procedure.
Has anybody any idea to resolve the problem?
Thanks in advance
BEGIN
DBMS_REPCAT.CREATE_SNAPSHOT_REPGROUP(
gname => '"MYGROUP"',
master => 'DB.DOMAIN.COM',
propagation_mode => 'ASYNCHRONOUS');
END;
CREATE SNAPSHOT "MYUSER"."MYTABLE"
REFRESH COMPLETE WITH ROWID
FOR UPDATE
AS SELECT "COD", "NAME" FROM
"MYUSER"."MYTABLE"@DB.DOMAIN.COM c
BEGIN
DBMS_REFRESH.ADD(
name => '"MYUSER"."REF3"',
list => '"MYUSER"."MYTABLE"',
lax => TRUE);
END;
BEGIN
DBMS_REPCAT.CREATE_SNAPSHOT_REPOBJECT(
gname => '"MYGROUP"',
sname => '"MYUSER"',
oname => '"MYTABLE"',
type => 'SNAPSHOT',
min_communication => FALSE);
END;

Hello,
These days I have had some problems with my forum-account and I haven't been able to connect and reply.
Regarding to your doubt, the name of refresh group was correct, and as I see, the problem can't be related to the refresh group.
While the problem with my account was resolved, I created two new databases (*) and the problem within the materialized view process is disappeared. I suppose that my first original databases were degraded, but I don't know where.
(*) of course, I could do that because I use Oracle in an academy institution, not for production, thank God
Anyway, for now I will give up here. Thanks for your help.
Regards,

Oracle Streams vs. Updatable Materialized View

Does anyone have an idea in which cases Oracle Streams is better than Updatable MV or visa verse?

Are you really talking about Updatable Materialized Views? Or multi-master replication? Personally, I'm rather hard-pressed to come up with a situation where updatable materialized views would be useful unless you're taking the next step and doing multi-master replication.
In general, Streams is going to put less load on the source system than materialized views and is going to replicate data more quickly. The downside tends to be that it's a relatively new technology, so it's not appropriate for environments that have older versions of Oracle. Going along with that, you'll find a lot more people/ organizations/ setups using materialized views than Streams, which can be a good thing if you need to hire new staff/ get support from a local user group/ etc. Streams also tends to be more flexible, which can be a good thing, but also tends to make things a bit more complicated.
If you can outline the particular problem you're trying to solve, we can probably be a lot more specific...
Justin

Update material doc.num in assignment field of GR/IR line item of a/c doc

HI Experts,
please tell me the solution for my problem
My requirement : Transaction is : MIGO
Before posting of material document, update material document number in assignment field of GR/IR line item of accounting document (WE) at number commitment stage
Update MKPF-MBLNR (Material Document Number) in BSEG-ZUONR
but already i tried AC_DOCUMENT i got a problem .
What i did,
first use MB_DOCUMENT_BADI with method
mb_document_before_update.
here i tried to get the material document and export into memory
after use AC_DOCUMENT With method
change_after_check.
here Import the material document doc num and pass it to Assignment field in
but it is not working
when i debug first trigger the AC_DOCUMENT And then it goes to MB_DOCUMENT_BADI
Plese help me regarding this.
Moderator message: please open only one thread per issue.
Edited by: Thomas Zloch on Feb 9, 2012

Hi,
Thanks, I will check the same. Well, I will be clearing the documents with reference to MIGO number itself. When I do my delivery chrgs migo, that number I need to be populated in my line item's assignment field. Not only that but I the same number should get populated in the delivery charges miro. Since my miro is with ref to PO it becomes difficult to fetch the field.
Plz let me know if you can help me on this as well.
Thanks,
Priyanka.

Background job finishes but error Error While Updating Material into Standard SAP5678

Dear
we run background job which finishes successfully but when we sqw logs it shows
Error While Updating Material into Standard SAP5678
Kindly share the reasons
Regards

This is an ERP Upgrade space and you should consider raising threads in the right space for prompt replies. Next time consider using SAP NetWeaver Administrator space for issues like these. Also you should consider closing your previous thread with the correct answer for future reference.
What I see is a custom job. You should check what the job does and also the trace file of the work process and the consult with the application team or the developer for more information. Unfortunately with that screenshot there is nothing much we can advice you.
Regards
RB

Material Replication filtering problem

Dear Experts,
we are working on SRM 5.0 Server 5.5 and we are facing following problem during material replication and delta download replication. After making all steps related customizing objects alignment between R/3 and SRM, we putted the filter using transaction R3AC1:
- Table = MARA
- Field = PSTAT
- OP = CP
- Low = E
- Inclusive indicator
Then we Synchronized the filter and checked on R/3 table CRMFILTAB: the filter entry was existing even if disappeared after running on SRM MATERIAL Initial Download (strange!)
Our expectation was to get all materials from back-end having purchasing views and linked to material groups replicated. Unfortunately the number of materials replicated are less !!!!!
Also we tried to make delta download and the above filter is not taken into consideration during delta download: all products modified on the back-end are replicated, also those materials without purchasing view!!!!!
What is wrong???? What should we do for making this filter working???
Thanks
#Bill J.

Vangala,
That's great!!! I tried to implement manually and worked very well,
Thanks a lot.You got 10 points.
#Bill J.

Update material master data BAPI_MATERIAL_SAVE DATA

Hi All,
I am using BAPI_MATERIAL_SAVE DATA Fm to update the material master data .
I want to change material type vend (which already existed) to HIBE material type .
Even though Basic data view populated its not updating in Material master .
Which views do i need to populate to change material type one value to other value?

if you use FM - BAPI_MATERIAL_SAVE DATA ,you can not update material type , use bdc program to update material type ,
See the transaction : MMAM - No BAPI to update material type
you need to use BDC Program.
Reward Points if it is helpful
Thanks
Seshu

Using the APD to update material master in CRM

Does anybody know if it is possible to update material master records in CRM from BW using the Analyses Process Designer with target CRM?
I would prefer to know this before creating a custom data target adapter in the CRM SPRO, writing all the required function modules and then finding out that it does not work.
Thanks,
József.

Which direction??
Inbound/Outbound
Inbound : IDOC_INPUT_MATMAS01

How to Update material cost of user defined org specific cost type

Hi,
We need to update material cost sub elements of an item for an org specific and user defined cost type.
I have inserted a sample row in the CST_ITEM_CST_DTLS_INTERFACE, and running open interface 'Mass Update Material Costs', but the program is not at all processing the rows, the Process_flag remains 1.
insert into cst_item_cst_dtls_interface
(inventory_item_id,
organization_id,
resource_id,
usage_rate_or_amount,
cost_element_ID,
Process_Flag ,
last_update_date,
last_updated_by,
creation_date,
created_by
values
(96023,
343,
52538,
0.00208012,
1,
1,
sysdate,
fnd_global.user_id,
sysdate,
fnd_global.user_id
Can someone help me out with this, thanks.
Regards
Dasu

I think there is some confusion.
"Mass Edit Material Costs" program is used to apply new activity rates to item costs. For this, you don't have to insert records in the interface. You have to define/update the new activity rates using screen.
To process records in the cost interface tables, you have to run the "Cost Import Process" program.
For more details, refer to http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/cst/settas06.htm
Hope this answers your question
Sandeep Gandhi
Omkar Technologies Inc.
Independent Techno-functional Consultant

Problem on Material Replication from R/3 to EBP

Hi friends,
I am having a problem on Material replication from R/3 to EBP. I had configured all the required settings in EBP as well as in R/3. Whenever we are starting initial loading R3AS I am getting outbound queues in EBP instead of R/3. I am getting the error like 'The current application triggered a termination'. I could able to replicate Vendor and Locations from R/3 to EBP. If anybody can solve this problem.
Thanx in advance.
Raj

Hi Ahmed,
Could you please elaborate. I am getting runtime error as 'Message_Type_X' (The current application triggered as termination with a short dump).
Thanks
Raj

Vendor and Material Replication from ECC6 Ehp7 to SRM7.0

Hi Experts,
I am facing an issue with replicating Material and Vendor Master from ECC to SRM system.
ECC system - ECC6.0 Ehp 7 & SRM system - SRM7.0
Middleware setting is done as per Note 720819 and performed the object like DNL_CUST_BASIS3 , DNL_CUST_PROD0, DNL_CUST_PROD1 and found Sucess in SRM R3AM1.
Errors :
1. Material Replication Error in SMW01
Mat. for Initial Download: Table not supported by function
Alternative units of measure are inconsistent; correct the values COM_PRODUCT_UNIT COMM_PR_UNIT
Alternative units of measure are inconsistent; correct the values
Validation error occurred: Module COM_PRODUCT_MAT_VALIDATE, BDoc type PRODUCT_MAT.
2. Vendor Replication Error in BBPGETVD
Backend systems with Release 740 are not supported
Message no. BBP_BUPA002
What are all the compatabilty issues will be faced connecting SAP ECC6 Ehp7 with SRM7.0? Can any one list down.
Please Suggest the valuable comments to resolve the problem as earliest.
Thanks & Regards,
Ramprakash N

Dear Ramprakash,
Please check below URL for #1.
Alternative units of measure are inconsistent; correct the values in SMW01
Please find the following note which might help you for issue #2.
1313972
1349825
1372175
Thanks
Shuvrajyoti

Updatable Materialized View and Master Table on same database

Hi all,
My first question - Is it possible to have an Updatable Materialized View and the associated Master Table located on the same database?
This is the requirement scenario:
One unique database D exists.
A is a batch table. Only inserts are allowed on Table A.
M is an updatable materialized view on Table A (Master). Only updates are allowed on M (no insert or delete).
Requirement is to push updates/changes from M to A periodically and then get the new inserted records from A into M via a refresh.
Is this possible? What other approaches are applicable here?

John,
My question is related to the implementation and setup of the environment as explained in the above example. How can I achieve this considering that I have created an updatable m-view?
If possible, how do I push changes made to an updatable m-view back to it's master table when/before I execute DBMS_MVIEW.REFRESH on the m-view? What is the procedure to do this if both table and mview exist on the same database? Do I need to create master groups, materialized view refresh groups, etc.?
One more thing.. Is there a way to retain changes to the m-view during refresh? In this case, only newly inserted/updated records in the associated table would get inserted into m-view. Whereas changes made to m-view records would stay as-is.
Hope my question is directed well. Thanks for your help.
- Ankit

Update material replication

Similar Messages

Maybe you are looking for