ChaRM and BI Transports

We have setup and configured ChaRM and started using it for an ECC Implementation Project and tested an ECC Maintenance Project.
However, Per OSS Note 1115759 (and experiences!), we do not use import all functionality for our SAP BI environment.
With ChaRM, it seems import all (or at least import all for the project) is used for both the implementation project and normal corrections of the maintenance project. We are not sure what to do for BI.
Does anyone have experience/recommendations for ChaRM with BI Systems?
Thanks!
Christine

Hello
You should first fix the errors you get such as the missing consolidation system
Please see thread [Re: No consolidation system found for SID in solman; or check the forum on the error message "'No consolidation system found for" and you will find relevant information.
I would advise to update your SAP Solution Manager though to one of the latest available levels, there are a lot of fixes and enhancements to Charm (and also availability of quality gate management which gives some of the functionality of Charm but is more compact).
Kind regards
Tom

Similar Messages

ChaRM: usage of ChaRM and none-Charm transport strategy

Hi ChaRM-TMS Gurus!
We have the following [SAP system landscape |http://www.file-upload.net/view-1086963/SDN_TMS_Ist_Soll.jpg.html] and would like to use ChaRM approach simultaneously.
What are the minimal requirements concerning transport layers/routes, which settings should be changed?
How much and which transport layer/routes does ChaRM need?
a) 1 any new transport layer/route
b) standard transport layer, transport layer "SAP" and others
Should all the standard transport layer/routes from virtual systems to real QAS and PRD systems or can I start as follows:
1) Leave the current TMS settings unchanged
2) Activate the extended transport control
Result: the current setting will be client specific and all the old transport requests will be moved to client specific transport routes
3) change the transport strategy (from mass transport to single transport)
3) Define new transport layer
4) Define new transport route for SAP objects from DEV to QAS
and assign the transport layer from 3) (client specific)
5) Define new transport route ZXXX from DEV to QAS
and assign the transport layer from 3) (client specific)
6) Define the delivery transport route from QAS to PRD (client specific)
7) activate and distribute the settings
Thank you very much indeed!
Thom

Hi Martin,
Solmaniacs' assumptions are correct. You can have as many source clients as you want.
As long as
- STMS configuration (transport routes, and domain links) are consistent
- SMSY configuration (logical components are declared properly with assigning the right role types to systems/clients)
- Project declaration are done correctly (so that from Solman solar_project_admin you can read the STMS as confiured in the distant STMS domain)
- IMPORTANT: those configuration GO ALONG with each other !! (SMSY should nt contradict STMS for example...)
The tasklist that is generated for each Solman project will be as follow
- Node 1: Header Tasks (commun to all systems)
- Node x: Corresponding to track x declared in Project (each Source System will have his own node with the corresponding track under)
- Node x+1
- Node ...
- Last Node : Tasks for Tasklist closure - checks on scma consistancy and CTS projects closure
So you'll always have n+2 nodes in your tasklist; n beeing the number of declared source (=dev) systems in project
For each action launched from change docuemnts like creation of TR, release of TR or Retrofit (as Solmaniac said) you'll have an additional pop-up that will appears letting you choose the system you want to use for the action
Hope its helpful
Regards
Khalil

Charm and transport sequence

Hi,
If I have corrections A, B, C and D containing changes to the same object. A was released as a transport first, B second, C third and D fourth. They go through testing and the workflow in Charm, with final approval sequence of D, C, A. D was quickest to get tested, perhaps simplest change. C was second and A was last, perhaps the one to test longest. B on the other hand looks like it will need more time. I want to import A, C and D into production. I want to do mass imports into my production system. Using Charm, how can I ensure that (1) correction transport sequence in the import queue is A, C and D (transport release sequence is obeyed) and (2) B is not in the production system queue (release of transport in dev system does not add it automatically into the import queue in production)?
Don't worry about low level detail description, I am after guidance/ideas on how to achieve this.
Thank you,
Mike

Hi Prashant,
if you use normale correction SDMJ with project import, the import sequence A, C, D is secured, since the transports are imported in the sequence they were released in the development system.
If you want to prevent to import B you can use transport of copies.
Regards,
Christoph
Edited by: Christoph Kronauer on Oct 19, 2010 10:20 AM

ChaRM and CTS+ for EP 7.0 in SolMan

Hi,
I've been trying to get CHaRM working for EP 7.0 in our SolMan systems for a while, but have not been able to get it working. I've read through and followed all the documentation on the resources page here, the Solution Manager documentation on help.sap.com and service.sap.com and all the notes I can find. We are running SolMan 7.0 SPS 17, and the Portal is on NW7.0 SPS 15.
I have configured SMSY, populated from SLD and assigned to a system (I've tried NETWEAVER 7.0 - Enterprise Portal main instance, and ERP 6.0 - SAP XSS main instance) and assigned the dev and prod systems to a locical component.
I have configured STMS, a single client independant consolidation route from dev to prod. The dev system is defined as a Non-ABAP "source system" in TMS, and I've set the communication system to be the solman system/client.
The CTS+ config all seems to work, I can create/release transports and add objects to transports from the EP dev system.
When I try to implement ChaRM, I create a new maintenance project. I add the portal landscape component to it, and activate change management. This works. When I try to create the task list, it fails trying to create the project IMG for the system. It gives me the error -
IMG project creation error -> see long text
Message no. /TMWFLOW/TASKLIST164
Diagnosis
You want to create a new maintenance cycle. An error has occurred.
When you create a maintenance cycle for a maintenance project in the Solution Manager (SMI project), a project is created in the Central Transport System (CTS project), per logical development system. This CTS project is required as an attribute for the transport requests.
A CTS project is always assigned to an implementation project (IMG project) in the physical system. There must be an IMG project in all physical systems in an SMI project, in which a system change (development/maintenance) can be made.
If there is no IMG project in a system, one is created automatically. The generated IMG project has the same name TEST as the SMI project, but there cannot be an SMI project and an IMG project with the same name in one system, for system-internal reasons.
In SMI project TEST there is a development system in the same physical system SMU as the Solution Manager.
System Response
If one of the development systems is in the same physical system as the Solution Manager, the IMG project cannot be created automatically.
Procedure
Create an IMG project manually in system SMU. In the path: SAP Menu -> Tools -> Solution Manager -> Project Administration.
Choose the SMI project TEST, go to the 'System Landscape' tab, and then the 'IMG Projects' tab.
Select an entry for the system SMU and try to create the IMG project. The system tells you that a system of the same name already exists, and asks you whether you want to choose another project name. Answer 'Yes', and change the project name.
You should then be able to create the task plan.
SMU (solution Manager) is not in the system landscape of this project, I expect that it is trying to create the IMG in this system since this is the communication system for portal dev. However, since it's not in the landscape, it isn't in the IMG tab to be able to create manually as described.
If I try to create the IMG project for the Portal Dev system directly in the project, I get the error -
Error getting RFC destination for logical system EPU
Message no. SMSY_PPMS_API044
Diagnosis
No RFC destination was found for the logical system 'EPU' .
System Response
The RFC connection to the system 'EPU' cannot be created.
Procedure
Create the required RFC connection in the Solution Manger System Landscape Maintenance.
Any advise would be appreciated.
Thanks,
James Blair

Hi James (and others),
I trust you have resolved your issues with ChaRM and CTS+.
If you are running a partuicularly extensive landscape you may want to consider a third party alternative to ChaRM.
Particularly one that integrates with CTS+ (to include non ABAP such as Portal, NWDI Java and so on).
There are several available, the one I am most falimiar with (Note: I do work with Revelation Software Concepts) is Rev-Trac and you can read user reviews at http://www.sdn.sap.com/irj/ecohub/solutions/revtrac
If you run an EcoHub search on Change and Request Management or similar the other alternatives should be returned.
Regards, Rick

Charm implemenation for transports in solman 7.1

Hi Guru's,
Can anyone help me to get knowledge in charm implementation for transports in solman.
I am new to solman , can anyone help here.
Help is much appreicated.
Thanks,
Pradeep.

Hi Pradeep.
Please check the following blogs:
http://scn.sap.com/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
http://scn.sap.com/people/dolores.correa/blog/2009/07/23/change-request-management-scenario-working-examples
http://scn.sap.com/people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
Thanks
Vikram

CHARM : Sequence of transport request to import

Hi,
I'm configuring CHARM and found out below issue.
Scenario.
1) Charm project with project type implementation was created in SOLMAN. The type of change is normal correction. All transport request was created under 1 task plan. The transport was created based on configuration and some of the transport request have dependency to others transport request.
For example.
a)GL account need to be created in FI and was assigned to TR002.
b) MM need to configure the GL account that was created in a) and was assign to TR001
Issue
When the TR was release, how do we ensure that the sequence of import to QAS client and PRD client must follow the dependency of the TR created?
Appreciate your input.
regards,
Biah

Hi Sir,
I am working in SAP Solution Manager. I would like to know some concepts regarding CHaRM:
Currently our project is using Transoport Proposal. We will soon shift using CHaRM. But I am not aware of the Technical concepts.
1. How to configure CHaRM with the Tranport Proposal Flow.
2. How to navigate in CHaRM? (screenshots can help).
3. I am aware of the process but still after creating a CHaRM how do the Developer navigate to do a change in DEV system.
will he go through CHaRM. (please explain me).
4. Also explain me the total process from technical point of view till the CHaRM closure.
5. I am aware of SOLMAN in this process where the Charm requests are collected and monitored.
Hope I will get a good guidance from your end....

CharM questions (mix Transport strategy)

Hi ChaRM-experts!
I plan to map the existing transport landscape into ChaRM scenario of SOLMAN and have the following questions:
1) Is it possible to combine ChaRM-functionality and still use the old transport settings (without ChaRM) for the same system landscape:
DEV --> QAS --> VO1 (Without ChaRM and with virtual system)
DEV:101 --> QAS:101 --> PRD:101 (With SOLMAN ChaRM)
Can e.g. the target group concept help in this situation?
2) Is it possible, after the CharM implementation, to allow the developers create transports in DEV system?
Thank you very much!
Holger

Hi ChaRM-experts!
I plan to map the existing transport landscape into ChaRM scenario of SOLMAN and have the following questions:
1) Is it possible to combine ChaRM-functionality and still use the old transport settings (without ChaRM) for the same system landscape:
DEV --> QAS --> VO1 (Without ChaRM and with virtual system)
DEV:101 --> QAS:101 --> PRD:101 (With SOLMAN ChaRM)
Can e.g. the target group concept help in this situation?
2) Is it possible, after the CharM implementation, to allow the developers create transports in DEV system?
Thank you very much!
Holger

ChaRM: combination of transport strategies

Hi ChaRM-experts!
I plan to map the existing transport landscape into ChaRM scenario of SOLMAN and have the following questions:
1) Is it possible to combine ChaRM-functionality and still use the old transport settings (without ChaRM) for the same system landscape, letu2019s say:
DEV --> QAS --> VO1 (Without ChaRM and with virtual system)
DEV:101 --> QAS:101 --> PRD:101 (With SOLMAN ChaRM)
2) What will happen with existing transport, transport in pipeline by switching into ChaRM scenario?
3) Is there some restrictions for the implementation of ChaRM for SAP R/3 4.7 systems?
Thank you very much!
Holger

Hi Holger,
1) Is it possible to combine ChaRM-functionality and still use the old transport settings for the same system landscape, letu2019s say:
DEV --> QAS --> VO1 (Without ChaRM and with virtual system)
DEV:101 --> QAS:101 --> PRD:101 (With SOLMAN ChaRM)
For Charm we need the transport route to be client specific.Once you have done the client specific transport route,you cannot use the older Transport route.
2) What will happen with existing transport, transport in pipeline by switching into ChaRM scenario?
TPs created before charm will be moved manually(normal process),as they will not be captured under charm project.
3) Is there some restrictions for the implementation of ChaRM for SAP R/3 4.7 systems?
No.
Please revert for any clarifications,
Regards,
Avinash.

Has anyone been able to successfully integrate CHARM and BW?

Has anyone been able to successfully integrate CHARM and BW?
We are trying to pilot it but cannot find a way of allowing us to control the sequence of importing transports - it's fine for small single transports but we can't see how to control the order of multiple transports or how to re-transport specific indiviual transports.
Thanks

You can but you have to install Rosetta from one of your (snow)leopard) disks. It's not a good idea if you don't know what you are doing. But it does work. There are some instructions online if you really want to give it a go. FCS2 is not native intel and Lion is not supporting PPC anymore. So while you can it is questionable if you should. Probably time to up or cross grade.
Pi

ChaRM with several transport layers

Hi!
We would like to use Solman ChaRM approach.
According to SPRO-documentation ChaRM only supports consolidation routes from standard transport layer.
We have besides the standard transport layer other transport layer and have the following question
1)What will happen when the developer try to change and import into QAS system object assigning to none-standard transport layer?
1a) ChaRM does not allow to change this object and the appropriate pop up window comes up
1b) ChaRM integrate this transport layer as standard transport layer
Any helpful information will be very appreciated
Thank you very much!
regards
Thom

Hello Thom,
I think, your question is almost independent from CHaRM. This is handled by the transport management system (TMS). If your developer changes the object assignment to a transport layer, and there is a transport track for this layer to the (same) QAS it should work. But if this QAS is not configured in CHaRM as a target system (in SOLAR_PROJECT_ADMIN), SolMan will probably raise an error message.
Also if the transport layer assignment / dev package not valid for this transport track, you will not able to release the transport -> SolMan is just using TMS mechanism and this will bring up an error message in CRMD_ORDER.
Unfortunately you can't see the transport logs in CRMD_ORDER directly, so the answer to 1a) is: In case of trouble releasing the transport you will get an error, but not the full error message.
1b) ChaRM cannot change a transport layer to a standard transport layer, this must be done using STMS on the transport daimn controller.
Regards,
Holger

ChaRm and CTS+ configuration

Hello Experts,
Can anyone forward ChaRm and CTS+ configuration document to me, I have received Business requirments and trying to configure the same. I would appreciate step by step configuration guide for both.
Thanks in advance.
Regards,
Swapnil Lakhe
lakhess<at>gmail

Hi,
Please find the below steps for Charm confirguration :
1.SAP Solution Manager Implementation Guide  SAP Solution Manager  Basic Settings  SAP Solution Manager System  Activate Integration with Change Request Management
Click on the Execute icon with the text Activate Integration with Change Request Management
Double click the Activate Change Request Management and set up client
It will show the following window type your Change Request Management Client Number
Click on the Integration Solution Manager
If you have different system for Change Request Management gives the RFC destination for that System.
Click back button
Double click on the Integration Change Request Management
You have to maintain the following data here
Column 1: Application: CHARM
Column 2: + : W
Column 3: RFC Destination: NONE
Column 4: + : CUST620
Column 5: + : 1.0
2.SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Standard Configuration 
General activities
Click on the Execute button with the text u201CActivate BC Sets u201C
It will take us to SCPR20 Transaction which is used to Activate the BC sets
Select the BC set SOLMAN40_CHARM_BASICFUNC_001 , it is for solution manager version 4.0
Click on the Activate Button
Create a Request for Activating the BC Set
Click Save button to assign with a TP .Other wise Create a new Transport Request (TP).
In Overwrite Data Box, select the Overwrite data, and in Activation Mode box select Expert Mode Option , Click on OK Button to activate this BC set.
3.SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Standard Configuration 
Transport Management System.
In Order to do all the Settings under the Transport Management System do follow the steps.
All the below settings has to be done in satellite system not solution manager
1.     Define Transport Routes for System Landscape
Go to Transaction STMS
Choose Overview -> Systems.
Double-click each system.
The Display TMS Configuration: System <system ID> screen appears.
Select the Transport Tool tab page.
If the entry CTC does not appear in the Parameters column, enter it there, and then in the Value column, enter 1.
Save your entries.
Configure Transport Strategy
Go to Stms Transaction
Go to Menu Overview  Transport Route
Doubt click on Each System . In the Transport strategy group box, select Single transports
(since only Import Single and Import Project All are used).
In the Quality assurance group box, deselect Delivery after confirmation
1.     Choose Continue.
Activate TMS Trusted Services
Choose Overview -> Systems.
Choose Goto -> Transport domain.
In Management Tab
In Security Options group box
Click on Trusted Services Active
Go to QA Approval Procedure
You should not assign any QA approval system there
Save your Entries
Call Transaction STMS.
Choose Overview  Systems. The system overview appears.
Choose SAP System  Create  Domain link.
The dialog box Request for Linking 2 Domains appears.
Enter the system name, host name and system number of the domain controller you want to link to, and then confirm your entries.
Your SAP System performs the following actions automatically:
o     Generates the required RFC destinations.
o     Sends the address data of the controller to the controller in the other domain.
You can now see that you have requested the domain link to the other domain in the system overview.
Click the Distribute and Activate TMS Configuration ICON on the Application Toolbar
After that Go to SAP System  Check  Connection Test, transport directory and transport tool
Check all once whether it is having inconsistency.
4.Check Configuration of Transport Domain
Log on to every domain controller that is connected to your transport landscape.
Call transaction STMS
Apart from the information "You are logged onto the domain controller", you should not be able to see other messages or warnings.
Generate RFC Destinations to Client 000
Call Transaction SMSY.
Go To Landscape Components
Go to your Satellite System
Click on the Domain Controller System
In the Right side Tab strip, Click on the Clients, Select 000 client Click on RFC generate Button
Give the User name for Read Access and Change Manager
Click the OK Button to Continue
Add Import Authorization to Operator/Administrator
Make sure that the operator and administrator users in client 000 of the target systems have the same name as their user in the Solution Manager   system.
Assign import authorization to the operator and administrator users in client 000 of the target systems (SAP_CHANGEMAN_OPERATOR and SAP_CHANGEMAN_ADMIN roles).
5.Set Project Assignment of Requests as Mandatory
If you want to enable your change request project is mandatory while creating a request for workbench or customization object, follow the steps
Go to Transaction
/N/TMWFLOW/CMSCONF
Select the Change Request Management System
Double click on the Project Assignment column
A new windows opened as follows
In the Attribute Required for Requests Box , Select Mandatory on the Default for all clients List
In the Client u2013Specific Setting Activate the tick mark of the Right side of the Table Control
6.Change Transport Request Option
Requirements
u2022     Repository changes are permitted in the system where you want to change the transport request option. (If they are not, proceed as described in SAP Note 327351.)
u2022     You do NOT use template projects.
Go to Transaction SE38
Enter the following Program   SAPLSCMA
Click on the Display Button
Click the Find icon and type the following keyword,
G_ACTIVATE_CORRECTION_SYSTEM
Click on the OK Button to search
Using Modification, Edit the Program in Change Mode
Delete the following lines ,
message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
And Insert the following lines ,
no_automatic_recording = 'X'.
Call Transaction SCC4
Select the Change Request Management Client and Click the Display ICON.
Go to Transaction SE 11
Enter the table SCMATREED
Choose Display
In Menu Click on Goto -> Indexes,
Choose Yes in the dialog box, and enter the index name 001, and the following short description: Index for Node in SCMATREE.
Maintain Number Ranges
Go to Transaction SNRO
Enter Object Name /tmwflow/M
Click on Number Range Button on the Application Toolbar
Click on the Change Intervals Button
For the new interval, enter 01, and use the F4 Help function to select a value for the From Number field.
The system returns 000000001 to 999999999.
Save the Entries
Come to the SNRO First Screen again; follow the same procedure for the following objects
/tmwflow/d and /tmwflow/v.
SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Extended Configuration  Schedule Manager
( Note in HLL We have using the Standard SAP Variants )
Create Customer-Specific Variant for Task Lists
Click on the Execute button
To Create a New Entries, Click on the Create New Entries Button
Type the Variant Name in the Variant Column Starts with the name space of u2018Zu2019, and in the Description Column you can maintain the description
Define Additional Tasks for Task Lists
Create Customer-Specific Header and Footer Tasks
Install Template Report
For all the above Refer IMG Node, follow the Steps
SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Change Transaction
Check Installation Activities
Make sure that you have performed the iBase IMG acitivities before you proceed with the Change Transaction IMG activities: SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> Service Desk -> iBase.
Check the all the following settings has been done .
Initially Create and Assign the Component Systems as iBase Components
Manually Create and Assign the Component Systems as iBase Components
Assign Business Partners to iBase Components
In the following Link all the Settings comes with BC Set.
SAP Solution Manager Implementation Guide  SAP Solution Manager  Scenario-Specific Settings Change Request Management  Change Transaction
USER Authorization
Administrator
SAP_CM_SMAN_ADMINISTRATOR
Change Manager
SAP_CM_SMAN_CHANGE_MANAGER
IT Operator
SAP_CM_SMAN_OPERATOR
Developer
SAP_SOCM_DEVELOPER
Regards
Sreedhar Reddy.A

ChaRM and test management in implementation projects

Hi
I am doing implementation projects in solution manager. i have activated charm in the project so as to transport all the changes related to the project with the project lifecycle.
I have got confusions regarding CHarm and Test MAnagement.. when we activated CHaRM the tester can logon to the system and perform testing and pass the Change Document to the next phase.
What is the standard flow when both CHaRM and TEst Management for a project exists??
Thanks

Please can someone tell me how to use TEST MANAGEMENT and ChaRM for Implementation Project together??
Edited by: Hasan Sidra on Jan 2, 2012 11:11 AM
Edited by: Hasan Sidra on Jan 2, 2012 11:11 AM

Tables for delivery and stock transport orders

Hi Members,
I have a requirement where i have to display (in a report output) a requirement quantity of deliveries and stock transport orders which are displayed in MD04 transaction for particular material and plant.
I don't know which tables these quantities sit into.
If you know please help.
Points will be suitably rewarded.
Reagrds,
Boby

>
Boby wrote:
> Hi Members,
>
> I have a requirement where i have to display (in a report output) a requirement quantity of deliveries and stock transport orders which are displayed in MD04 transaction for particular material and plant.
> I don't know which tables these quantities sit into.
> If you know please help.
> Points will be suitably rewarded.
>
> Reagrds,
> Boby
if you only have to display deliveries and stock transport orders you can take LIKP and LIPS for the deliveries and LTAK and LTAP for transport orders.
for all the other elements displayed by MD04 we would have to know about your setup: are you using dispo-areas (which would populate tables MDMA ...) so in that case please provide more information.

SOAP Use Adapter-Specific Message Properties and Variable Transport Binding

Hi Friends,
   I am new to use to Soap Adapter. Please help me out bellow doubts.
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
   2. Where exactly we r using below parameters.
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Thanks&Regards
G.Bhanuprakash

Hi,
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
SAP Help says both are needed to be checked when you want to process adapter attributes
Configuring the Receiver SOAP Adapter - SAP NetWeaver Exchange Infrastructure - SAP Library
These attributes can be get/set using dynamic configuration and their technical names are what you have pasted:
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Remote User - the username used to send a message to the adapter engine using SOAP
Remote Host - hostname which the remote user used
SOAP Action - SOAP Action of the XI webservice (sender) / SOAP Action of the receiver webservice
Variable Headers are additional key-value pairs in the HTTP Header that could be accessed in the XI Header using dynamic configuration. The limit is only three though.
Regards,
Mark

Procurement cycle in third party order and stock transport order.

please provide me in steps the procurement cycle in third party order and stock transport order.

Hi,
STO Process: -
1.Create a vendor for the company code of receiving plant, using account group :0007 using T-Code XK01.
2. Assign this vendor to Delivering plant
Go to XK02 >Purchasing view>Extras>Add. Purchasing data>Plant
3. Create internal customer with the sales area of the vendor. Go To XD01
4. In Pricing procedure determination relevant to STO, assign document Pricing Procedure and customer pricing procedure appropriate for STO to get the pricing in the invoice.
5. Maintain condition records for the relevant pricing condition.
6. Some more setting for STO: Go to MM> Purchasing > Purchase Order > Set up STO > define shipping data for plants > Go to Receiving plant >assign customer here & Supplying SA (for billing) to Receiving plant here
7. Go to MM > Purchasing > Purchase Order > Set up STO > define shipping data for plants > Go to Supplying plant and assign the sales area of receiving plant.
8. Go to MM > Purchasing > Purchase Order > Set up STO > assign delivery Type & Checking rule
Assign the delivery type to document type. In this case, Delivery type NLCC is assigned to Document type NB
9. Go to MM> Purchasing > Purchase Order > Set up STO > Assign document Type, One step Procedure, Under delivery tolerance
Assign the document type NB to supplying plant and receiving plant
10. After all settings , Create the STO using T-Code:ME21N and maintain pricing conditions of freight and Save.
11. Create Delivery :VL10G
Click on the Background Button after selecting line item
A message is flashed : See log for information> next Click on Log for delivery creation Button >click on line item>click on document button to get Delivery document No
12. Picking, PGI:VL02N
13. Billing:VF01
Save the document and its done
14. J1IIN - Outgoing Excise Invoice
15. MIGO - Goods Receipt against outbound Delivery
16. J1IEX - Capture & Post Excise Invoice
Pricing configuration for STO: -
In SPRO > MM > Purchasing > Conditions > Define Price Determination Process > Define Schema Determination > Determine Schema for Stock Transport Orders > Here assign Calculation Schema "RM2000" i.e. Stock Transfer Document to Schema Grp Pur. Org, STO Type (For e.g. UB) and Supplying Plant.
Calculation Schema "RM2000" has condition type P101 which will pick up the MAP of supplying plant automatically during creation of STO in ME21N ("Conditions" Tab).
You can create new freight / delivery cost conditions in M/06 and assign in pricing procedure "RM2000" in M/08 and also assign the Accrual Key to this and do the Account Determination for this Accrual Key in OBYC
At the time of PGI, following accounting entry will get generated;
Stock A/c - Dr - 110 INR (Receiving Plant)
Stock A/c - Cr - 100 INR (Supplying Plant)
Freight Clearing A/c - Cr - 10 INR (Supplying Plant)
Third Party Process Flow: -
1) MM01 - General Item category Group should be BANS in basic view of material master.
2) VA01 - Creation of sales order with VA01 transaction in SD module
3) When sales order is created system automatically creates a PR for the material with item category as "S"--> Third Party Item
4) ME21N - Directly PO with item category as "S" and delivery address as customer address
5) MIGO - Statistical GR by MM ( When it is made goods are received and delivered)
6) MIRO - Invoice by MM for vendor
7) VF01 - Billing by SD on Customers

ChaRM and BI Transports

Similar Messages

Maybe you are looking for