Travel request release strategy reg

Hi,
How to create Travel Request Release strategy.

Hi,
If its TR for Release strategy,then follow this process
In golden client , its automatically cretaed/ saved in TR.
You have to create characterstic/class in all clients
Regards

Similar Messages

Down Payment Request Release Strategy

Dear Guru
Is there any functionality Can we put the release strategy in Down Payment Request of vendor . once it has been released by authorised user it can pay by accounts dept using T.code F-48 or F110.
Waiting for response.
Thanks & Advance
Edited by: kpkreddy on Mar 5, 2010 3:51 PM

Hi Reddy,
I don't think there is standard SAP functionality of release strategy for Down Payment Requests. You may need to setup a workflow for this, then post the down payment and so on.
Kind Regards,
Kiran Yelamarthy

Transport request in PR release strategy

Hi Experts,
While configuring characteristics and classes for release strategy in PR, system is not giving prompt for transport request.
What could be the reason? Is it standard functionality or something has to be done at our end.
Kindly suggest
Rgda

Hi,
Check the following SAP notes.
10745
45951
86900
Hope it helps,
Regards,

Can i transport PO Release strategy in a request

Hi Gurus,
I have done po release starategy in dev can i transport the release strategy in a request to quality client or should i do the same setting again in quality server.
Regards,
Dheepak

hI
1- Release classification is a master data which you can not transport and need to maintain in each client.
2- Goto Txn -- CL24n in Qly or PRD
3- Enter release class and class type then enter ,there you will get all your strategies select the strategy you want to maintain and details there you can maintain the values.

Release strategy for Transport requests

Hi,
Can anybody give me the detail steps to configure release strategy for transporting requests?
we are having Dev and Prd systems.
Regards,
Vinnu.

Hello,
I hope you have configured TMS for two system landscape.
Just make the transport routes also, make DEV system as a Domain Controler.
Then transport requests will automatically come in to the request queue.
Using tx stms_import , import those request sequentially !!
Note: Points always encourage me to reply !!

Reg.Release strategy for particular vendor

Dear Friends
We have 500 vendors, the release strategy is aplies to all but the Release strategy should not be applied for particular one vendor.
that is w/o release strategy that vendor has to work(if we raise PO the release strategy should not be applied)
Pls help me
Thanks
Rajakumar.K

Vendor master is dynamic and if you define it as a character value, then you need to keep on adding the vendor numbers.
as and when the new vendor is created.
if you use the purchasing group as a character, then what happens if another user creates PO with different purchase group.
you need to think about the below options.
1. Define release process based on purchase group XX as suggested by many , but use BADI ME_PROCESS_PO_CUST
and write the logic in such a way that, do not allow to save PO if the purchase group is not equal to XX.
2. Use BADI ME_PROCESS_PO_CUST and write your logic in such a way that for that vendor it should not refer table CEKKO

Release Strategy Get cancelled - Reg

Hai,
We are in SAP R/3 -ECC 6.O
Release stratgey has been set for the Purchase order and its works well for so many years.
The issue is , Some of the P.O alone , when the Header Terms & condition changed , Like adding one text line, or Some space or some dot, comma, The Release Strategy gets Re - Triggered ( Plz mind that , i have not changed any P.O Qty / Value/ Organisation entities/ Material Group/ Material/Tax code)
Kindly update , The reason - Why Release strategy gets re triggred for the , already Released P.O.
Regards,
PS

Release strategy gets retriggered only in case you have changed the amount or qty thereby increasing the amount of the PO
but as you say that you have not changed any thing which will impact the amount of the PO but the RS still gets re-triggered then we are left with only one option that some user exit has been active for this or some BADI please take help of abaper to find out the exit for this

Reg: P.O Release Strategy Changes

Hi All,
Release strategy is configured for a P.O.The changes in terms of releasing the P.O can be viewed in P.O Screen---Environment -
Changes.
Do we have any table for checking the changes made to a P.O in terms of Release strategy?
Have a Nice Day.
Regards,
RaviKumar.S

Hi,
You can check this in CDHDR table.
If version management is active for your PO then you can check the changes in EREV table.
Regards,
Bharat

Reg PO Release Strategy

Firstly Release strategy for PO is configured.
Now they are asking for new release codes to be added to the old ones.
The issue is when i am configuring this
old PO's no probelm as they are released.
new PO's no problem.
The issue is with OPEN PO'S .The new release code is going and sitting there but no PEN MARK will be there.(It is simply GRAYED OUT).so this creating problem for OPEN PO's.
How to overcome this.
with regards,
Patil Mallik

You didnot understand my problem.the problem is suppose there are 3 release codes previously.now only 2 release codes has released the PO.Still one release code yet to release.
now if i configure the new release strategy with one more New Release code.That New release code will come and sit in this Open PO(whose two release has happened and waiting for 3rd release) without having Pen symbol to release it is infact grayed out.
This should not happen i think.
for this there is any solution.this wont effect my procurement process.but the job of 4th new release code is done by 3rd release code which is not correct at the time of audit etc etc.
Any work around for this.welcome your suggestions and answers.
with regards,
Patil Mallik

Travel Request approval reg

Hi,
Can you pl.guide me how to config Travel Request approval process.
Thanks in advance

hi
you have to assign the Approval role to the approring authoriity user id.
activate the event linkage for workflow
assign the User ID.

Reg: Release strategy

Hi Experts,
I am now doing rollout project.
We copied the earlier configuration & dumped it.
Now we r in testing phase.
I configured released strategy for PO.
First I created charecterstics & then assign all to my class with class type 032.
Then inT code OMGS i configured every thing but when I am creating PO release strategy is not triggering. Same time also system is not throughing any error.
Please can anybody guide me in this regard.
Thanks in advance
Regards
Nayak

Hi dibyajyoti nayak ,
Check this
Go to SPRO > Materials Management > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Check Release Strategies
Also checkcharacteristic CT04 for additional data.
Hope thsi will solve your problem
Thanks and regards
Gitesh

Contract & PO Release Strategy

Hi All,
We are in the process of designing the release strategy for contract and PO. I would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
The release conditions for Contract required are
1)Porg
2)Pgroup
3) Value
Also, for quantity contract how can we make the release strategy trigger based on value.
The release conditions for PO required are
1)Porg
2)Pgroup
3)Material Group
4)Value
The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
Request your help.
Regards,
Kannan

Hi Kannan
Yes your requirement is possible...
While creating Charectristics in CT04 for External Purchase Documents...Create one more Value for your Document Category...ie) Table as :CEKKO and Field as BSTYP and choose the Purchase Doc. Category values K and F.
Then create Charecteris for CEKKO - EKORG, CEKKO - EKGRP and CEKKO - GNETW, CEKKO- MATKL... and assign these all 4 Chareteristices in your release class.
And Configure your release statergy according to your requirement...
Reward if useful
Regards
S.Baskaran

PO and SchdAgreem Release Strategy at Item Level

Hello!!
I have the request to setup a the release strategy for the PO and Schedule agreements at line item level....
as far I know for PurReqs is possible to do that... but for PO and SAs it is only at header level...
Do you know if is possible to do that in configuration??

Hi,
Release strategy for PO & SA is only at Header level, since these documents are external purchase documents.
But, PR is internal purchase document and release strategy is possible at both item and header level.
i think, it is not possible to do release strategy at item level for PO & SA as you said,
Regards,
Srinu.K

Error when creating a travel request with Advance amount

Hi Gurus,
When I create a travel request with an Advance amount and try to save the same, the system throws up an error msg : "Trip country does not exist in the system (T005).
However, it allows me to create the travel request without this error if i dont enter any advance amount in the travel request.
I checked the tables V_T706L and V_T706O and found my trip county to be existing.
Regards
Prakash

Hello Prakash,
The following are the prerequisites for transferring trip costs to accounting. In other words when you try to create and save a travel request with advance you are involving accounting entries and therefore the following needed to be checked:
1.Travel Management and Accounting are both at Release 4.5A. If at least one of the systems
has a release level lower than 4.5A, follow the instructions in Customizing for ALE.
2. For payment to be effected, vendor accounts must exist in Accounting for the respective
personnel numbers.
3. The following Accounting tables must be replicated in the Travel Management System using
Customizing transports:
Company Codes (T001)
Countries (T005)
Input Tax Codes (T007A, T007S)
Document Types (T003)
4. The transfer of settlement results
More relevant in your case would be the point 3. Countries(T005) not defined in TM.
Hope the above provided you more information.
Rgds
CONMJI

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

Travel request release strategy reg

Similar Messages

Maybe you are looking for