Clarification on SAP Note 612132-Stock consistency between serial & MM-IM

In the above Note 612132 SAP Question Number 3 is as under:
Question:
How do I achieve a consistent initial status if I have already (inconsistent) stocks?
Answer:
With the execution of a complete physical inventory under required serialization conditions, all stocks are serialized or existing inconsistencies are corrected.
Can anybody explain the steps to be performed to achieve this consistency.
Regards
Rajkumar Reddy
Edited by: Rajkumar Reddy on Aug 26, 2009 8:51 AM

Hi,
What is the volume of data you copied. Also have you followed the best practice of minimal/no activity in the source client.
The dictionary differences seems to be becuase of some SPs not applied in your ECP system yet
Regards,
Sanujit

Similar Messages

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

Clarification on SAP note 835466

Hi,
I need to proceed with the SAP note 835466 and I would like the clarification on steps # 3 and # 9 from it.
The prerequisities note 834897 and the relevant application were applied already.
Please can someone on this one?
Thanks.

Hi,
I understand it in that way.
You SP level is too low to be able to implement the note correction.
You have first to update at least to SP 55 before being able to implement the note correction.
That is one of the reason, to import regularly Support Packages.
Regards,
Olivier

Need clarification on SAP notes

Hi,
I need information on SAP notes relation.
Suppose a note X says corrections are delivered in the attached correction instruction, then its enough if we implement that specific note X.
If we go to correction instruction then it may have several other notes, do we need to implement all those notes specified in correction instruction 1st and then implement main note or directly we can apply Main note X.
If we apply main note obvisoulsy all the notes within correction instructions will be implemented
Regards,
Ravi

Hi Ravi
Suppose a note X says corrections are delivered in the attached correction instruction, then its enough if we implement that specific note X.
=>Before implementing those correction verify whether that X note applicable to your system release. Also verify is any manual code correction instructed in that note.
If we go to correction instruction then it may have several other notes, do we need to implement all those notes specified in correction instruction 1st and then implement main note or directly we can apply Main note X.
=> Before implementing those correction verify whether that X note applicable to your system release or its already implemented in your system. All these Prerequisites need to implement before final correction.
If we apply main note obvisoulsy all the notes within correction instructions will be implemented.
=> No we need to implement Prerequisites notes before main notes.
Thank

Clarification on SAP Note 961897

Hi,
We are currently on SAP BASIS 620 --> SAPKB62052.
With regard to the SAP Note 961897, it has been mentioned that the problem mentioned in the note has been solved in SAP BASIS SAPKB62062, I understand that, if our SP is below SAPKB62062, then we should implement the note corrections.
But, If we go and see the correction instruction 803799 relevant for 620 release, it has been mentioned that the correction instruction is only valid for SAPKB62055-SAPKB62061.
Just to try out, I also downloaded the same note through SNOTE and the note has become grey and says this note can not be applied.
1 --> Is that means this note need not be applied for SAPKB62052.
( means the reported problem is irrelevant for SAPKB62052)
(or)
2) --> or the correction instructions for SAPKB62052 is not yet released and we should wait
Appreciate feedback from someone who faced the same problem.
Thanks & Regards,
Raghunahth L

Hi,
I understand it in that way.
You SP level is too low to be able to implement the note correction.
You have first to update at least to SP 55 before being able to implement the note correction.
That is one of the reason, to import regularly Support Packages.
Regards,
Olivier

Clarification on SAP Notes 1873559

Hi,
I want to clarify something about 1873559 - B1iF_Using the DB Purge Tool for Database Size Reduction.
In Step 9, it says:
Shrink the integration framework database (e. g. using SQL Server Management Studio 'Shrink' option).
Under the Shrink task, there are 2 options, Database and Files. Which one to choose?
Either which, will the shrinking help to reduce the size of the mdf file? Because the Intercompany mdf file is now over 40GB and the C drive is running out space.
Please advise how to reduce the size of the mdf file (not just the LDF file).
Thanks.
Regards,
Richmond

Hi Richmond,
Choose shrink database as it will shrink both .mdf and .LDF file.
Regards,
Qiaoli

SAP Note 1504204 - TR: Divergences between 941 and Schedule B

We just implemented this note in our Development system and now when I attempt to generate a 941 report, I get a Syntax Error in Program 'RPCTRPU0". Was wandering if anyone else has experienced any problems once this note was implemented?
Thanks,

Hello,
Could you please provide more details on it? Did you perform the manual steps described in this note? If so, the user that you use to create the form fields has authorization to maintain data dictionary? You can check if the fields are created in SFP transaction and also in SE11.
Hopefully this helps.
Kind regards,
Graziela Dondoni

Related to SAP Notes Implementation

Hi Guys,
I have a dbt and need a clarification on SAP Note.
How I will be able to know by seeing the SAP Note or how I can judge my self that either (SAP Note) should be implemented thru manually or using SNOTE transaction.
Regards,
Ravi Ganji

hi Ravi,
SNOTE Transaction is available from 4.6C version owards only ... and to know whether you have to apply it manually or through SNOTE you will have to confirm it by the user ... for details refer
OSS Note
http://www.sappoint.com/basis/.pdf
http://www.sap-img.com/basis/oss-notes.htm
http://www.sap-img.com/basis/manually-applying-the-oss-note.htm
Regards,
Santosh

Date option in stock reversing program(SAP NOTE 175842)

Hi Gurus,
We have prepared a program with SAP NOTE 175842 for reversing stock posting.My client has done GR in march 09 and quality peoples have posted to unrestricted stock in same month.Now because of some reason stores person want to cancel GR. So we have reversed the posting for the lot in April using the programme.Now when stores person try to cancel GR in month of march system is giving error "Deficit of SL St.in QI prev. 14.800 MT ".Because we have reversed the posting from unrestricted to quality in april and we are trying to cancel GR in March system is giving above error.
Is there any settings such that in stock reversing program we can enter the date, so that on a particular date we can reverse the stock.Because in current situation we can enter lot no. only or is there any other solution to overcome this situation
Regards
Amit

hi amit
Yes system will not allow you to cancel GR for March when Reversal stock posting was done in April.
Because it will consider the status of stock when GR was made.
Which movement type you have used for reversal From Unrestricted to Quality.
Was it the activation of 08 & then 322.
If it is so then cancellation of GR will not take place through original GR document(as it is in unrestricted), It will give error msg if you give reference of same.
Even GR can not be cancelled based on 08 inspection lot as 08 is not wrt PO.
Just asuggetion explore User Exit
QEVA0008 Usage decision: Customer function key (e.g. to cancel UD)
Sujit

SAP Note clarification

Hello Guys
I came through a SAP note that, in extended classic scenaio 'do not have the need to create SAP MM Purchase Requisition or Stock Reservation from the SAP SRM Shopping Cart''
Please let me know why.
Thanks in Advance.

Hello,
With Extended Classic Scenario, follow-on document for a Shopping Cart is always a Purchase Order.
This PO is first created in SRM, then replicated to the backend system. Reason why PO can be modified only in SRM system: you cannot edit corresponding PO in MM.
With Classic Scenario, follow-on document for a Shopping Cart can be:
- a Reservation,
- or a Purchase request,
- or a Purchase Order.
Those three kind of purchasing documents are always created in the backend system where you can modify them.
Regards.
Laurent.

Stock Transfer between 2 different instances of SAP

Hi for all,
I want to know if anyone has any documentation about how to do a Stock transfer between 2 different instances of SAP, the worst part that I think is how to see a plant from one SAP to another, any collaboration will be appreciate.
Edited by: Ruy Osório de Freitas Neto on Mar 5, 2008 6:24 PM

I still don't see the difference between what you are telling me and the material i handled to you....
This material exactly describes the case where you have to wharehouse working in whatever ERP systems at the same time.
The ALE configurations are only one step between them.
The idoc types for purchasing are ORDERS, ORDRCHG,ORDRRSP, Quotes
For LE are Desadv,Shpmnt
Processo
Entrar um movimento de mercadorias no sistema ERP.
O sistema cria automaticamente um recebimento ou uma entrega com base nesse movimento de mercadorias.
O sistema transfere o recebimento por meio da BAPI InboundDelivery.SaveReplica (a entrega, por meio da BAPI OutboundDelivery.SaveReplica) do sistema ERP para o SAD, onde representa uma solicitação ao depósito para armazenar ou retirar mercadorias.
No sistema descentralizado, uma ordem de transferência no depósito é criada para a entrega ou para o recebimento, respectivamente.
Executar a entrega/recebimento físico(a) das mercadorias.
Confirmar a ordem de transferência no depósito.
Após a confirmação da ordem de transferência no depósito, é lançada a entrada de mercadorias para o recebimento (ou saída de mercadorias para a entrega). Isso libera a posição intermediária.
Essa atividade inicia a confirmação para o sistema ERP por meio da BAPI InboundDelivery.ConfirmDecentral para o recebimento e por meio da BAPI OutboundDelivery.ConfirmDecentral para a entrega.
O lançamento da entrada ou saída de mercadorias no sistema ERP ocorre automaticamente quando a confirmação é registrada no sistema.
Quando a entrada ou saída de mercadorias é lançada no sistema ERP, a transferência de estoque é lançada simultaneamente na Administração de Estoques.

Intra-company stock transfer between two ERP Systems without SAP APO

Hi,
I'm looking for information regarding the scenario Intra-company stock transfer between two ERP Systems without SAP APO.
On help.sap.com, I can only find below image, but I'm actually looking for the configuration settings required to implement it.
Does anyone have experience with this scenario?
Thanks & regards,
Oliver

Hi Jagdeep,
Thanks for the reply. I understand that I need to use iDocs and setup communication between both systems. What I am actually looking for is detailed information on the setup of the purchase order type and sales order type. Especially because there is no invoicing involved in this flow.
Regards,
Oliver

Clarification on Canada Year End SAP Note : 1658938 and 1662043

Dear All ,
We are currently doing yearend SAP note updates for Canada and need clarification on Canada Year End SAP Note : 1658938 and 1662043 .
SAP Note : 1658938 is with yearend delta transports which needs to be applied ,but it is mentioned that we need to apply all Year End related notes released on or before December 15th before applying the Delta transports.
My query is that Note 1662043 released on 12/12/2011 whether this needs to be applied before or after applying delta transports mentioned in 1658938
Pls help us on this .
Thanks
Muthuraj

Hello Muthuraj,
You need to apply note 1662043 the note before applying the delta transport.
I hope it clarifies.
With Regards,
S.Karthik

Difference between Ecc 5.0 and Ecc 6.0 SAP note number

Hello Friends,
Is any one knows difference between Ecc 5.0 and Ecc 6.0 version released SAP notes for FICO module.
Thanks in advance for your help
Thanks,
Ratnam

Hi,
Check these
Technical difference between 4.7 and ECC 5.0
difference between sapr/3 4.7 and sapr/3 ecc 5.0
Differences b/n 4.6c,4.7 and ECC 5.0
Regards
vijay

SAP Note 23345 for Oracle Consistency Check

Dear All,
I would like to run a Consistency check using backup type = online option via DB VERIFY but unfortunately each time I run the backup online using the below commands I am getting permission error.I have run the commands below using ORA<SIDADM>
brbackup -u / -m all -w only_rmv -e <parallel degree> -c
brbackup -u / -m all only_dbv -c -t online -e 3
brbackup -u / -m all -w only_dbv -e 3 -c
brbackup -u / -c force -w only_dbv -t online -p init<sidadm>.sap -m ALL -e 3
brbackup -u / -c force -w only_dbv -p init<sidadm>.sap -m ALL
I hope someone could provide what is the best command to use in order to execute the Consistency check in Online mode as I am planning to schedule it on weekly basis with the Online option..
Thank you.
Regards,
John

Do not double post the same question in different forums:
SAP Note 23345 for Oracle Consistency Check
Markus

Clarification on SAP Note 612132-Stock consistency between serial & MM-IM

Similar Messages

Maybe you are looking for