Changing PR request date

Hi all,
When we create a PR in the PR line item 'Quantities/Dates' tab the request date field gets the system date.
i.e The date on which PR line item is created.
Now let us take that a PR contains five line items. And I am creating the PR on 08/10/2009. So by default
request date field will get the date as 08/10/09.
Now I will change the request date on first line item as 30/09/09. Now the entered date should get copied to
request date fields of rest of the four line items entered in that PR.
This activity should happen before saving of PR.
Are there any possiblities to achieve the requirement?
Regards,
Partha

Have you checked any changes made to PR.How can you confirm the PR date changed ? Requisation date is PR creation date .Once you create PR it is not possible to change it to another date.

Similar Messages

Schedule lines are not modified when i change the requested delivery date

Hi
i have a issue when i am created sales order with requested delivery date 10.11.2011
and the same is copied in to item schedule lines as a 10.11.2011
before saving the order i change the requested derlivery date to 11.11.2011
this new requested delivery date is not dopied to schedule lines at item level (still is having 10.11.2011)
can any one tell me this is system standard behaviour or can we correct this
Thanks and Regards
Kishore

Hi DevarapalliKK,
I tried this solution & problem is solved.
--Go to VA01 & enter the material & qty
--Select the line item in VA01 & click on Edit
--Select Fast Change of & click on Delivery date & mention the Delivery date as 11.11.2011. & click on copy.
--Check the request delivery date in header level in sales tab it will change to 11.11.2011 & also check the Schedule lines in Item level the date will be 11.11.2011 & Save it.
Please let me know if your problem is solved
Regards
Pradeep

Mass change of pricing date and billing date in credit memo request

Hi,
Can i change the billing date pricing date on credit memo request docs using MASS transaction?
If i enter the regular sales order number it prompts me to change the value but if i enter the credit memo request doc number,the message "No data meets the selection criteria" is displayed.I also checked with IDES ,message is the same
Is there any different way to do mass change for credit memo requests or am i missing something here.
Please Suggest
Thanks
Abhilash Nayak

Hi,
Go to the transaction code MASS and enter the OBJECT TYPE as BUS2032 and enter
It will lead you to the next screen where you can find the Table and Field TABS
Select the SALES ORDER HEADER DATA and choose the fields data and choose the fields PRICING DATE and BILLING DATE and execute
In the subsequent screen you can see the selection screen where you can enter all the Sales documents for which you want to change
Key in all the documents and execute
Now change the date as per your requirement and check the effect
regards,
santosh

How to change the requested delivery date when approval has been done

Hi
We use SRM5.0 and we want to implement SC, now we want to make it possible to change the delivery date in the shopping cart when we approve.
This is needed if we request today but the approver didn't approve same day, therefore the requested day has to move the same number of days, that the approver has spend. Or else the deliver date will not be correct.
Do any of you know how to do this??
Best regards
Jakob

Hi Jakob,
What scenario do you use? Classic, Extended Classic, Standalone?
So depending on your scenario you can have differente types of follow-on documents (PR/PO only in ERP in case of Classic, or PO in SRMand ERP in case of Extended Classic).
Do you use Sourcing Cockpit?
I've tested this scenario in SRM 7.0 Standalone and if the follow-on document (in my case, a PO) is not "Ordered" yet then I can change the SC. But if it is already "Ordered", I can't change the SC. This is standard behavior.
You could use Sourcing Cocking to solve this issue, in this you don't use it yet.
Best regards,
Christian Zeuch

Mass Change to Requested Delivery Date

Hallo Everyone,
We have a scenario where we want to change the Requested Delivery Date to all Line Items when it is changed in Header Level.The reason is we might have 80-120 Line items in a Order.It is difficult for a person to change the req. delivery date for each line item.
Can any one tell me is there any standard way or FM to do ?
Thank You in advance.
Regards
RR

Hi Stephen ,
Thank You for your quick response , i did exactly as you have guided .I havnt see anything that does match .
And forgot to mention in my first message ,but some times i need to able to change one or two items manually . If i use BADI is it possible ? to change a one or two line items manually ?? as i am concerned when i save it again the BADI will trigger back line item requested delivery date to header level ?? Please guide me .
Thanks
RR

Change Travel Request Is Not Working

Hi all,
I am getting one error for that i need your help.
I have created one travel request ( I am using satandard ess application) , after
creatting travel request i am able to view the created trip , but when i select the created
trip and click on change button to change the request i am getting following error
500 Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
*Failed to process *
and in trace i got following error
Full Message Text
Exception occured during processing of Web Dynpro application sap.com/ess~tra/AllMyTrips.
The causing exception is nested.
[EXCEPTION]
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
at
com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFC
ModelClassExecutable.java:98)
at com.sap.xss.ser.xssmenu.fc.MenuLinks.getServiceLink(MenuLinks.java:232)
at
com.sap.xss.ser.xssmenu.fc.wdp.InternalMenuLinks.getServiceLink(InternalMenuLinks.java:365)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.getServiceLink(FcXssMenu.java:406)
at
com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.getServiceLink(InternalFcXssMenu.java:491)
at
com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.getServiceLink(FcXssMenuInterface.java:264)
at
com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.getServiceLink(InternalFcXssMenuI
nterface.java:429)
at
com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.getServiceLink(InternalF
cXssMenuInterface.java:586)
at
com.sap.pcuigp.xssutils.navi.FcNavigation.getNavigationTargetServiceWithKey1(FcNavigation.j
ava:524)
at
com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.getNavigationTargetServiceWithKey1(In
ternalFcNavigation.java:390)
at
com.sap.pcuigp.xssutils.navi.FcNavigationInterface.getNavigationTargetServiceWithKey1(FcNav
igationInterface.java:271)
at
com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.getNavigationTargetServiceWi
thKey1(InternalFcNavigationInterface.java:182)
at
com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.getNavigationTarget
ServiceWithKey1(InternalFcNavigationInterface.java:314)
at com.sap.xss.tra.fc.utils.FcTraUtils.startApplication(FcTraUtils.java:596)
at
com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtils.startApplication(InternalFcTraUtils.java:32
9)
at
com.sap.xss.tra.fc.utils.FcTraUtilsInterface.startApplication(FcTraUtilsInterface.java:334)
at
com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface.startApplication(InternalFcTraUtil
sInterface.java:260)
at
com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface$External.startApplication(Internal
FcTraUtilsInterface.java:489)
at
com.sap.xss.tra.vc.allmytrips.VcTraAllMyTrips.tripComponentCreate(VcTraAllMyTrips.java:518)
at
com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTrips.tripComponentCreate(InternalVcTra
AllMyTrips.java:438)
at
com.sap.xss.tra.vc.allmytrips.AllMyTrips.onActionCreateChangeExpRepFromRequest(AllMyTrips.j
ava:444)
at
com.sap.xss.tra.vc.allmytrips.wdp.InternalAllMyTrips.wdInvokeEventHandler(InternalAllMyTrip
s.java:628)
at
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.
java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseMo
del.java:420)
at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.j
ava:132)
at
com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.jav
a:335)
at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSessio
n.java:319)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(Clien
tSession.java:733)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSessi
on.java:668)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250
at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:1
50)
at
com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHa
ndle.java:73)
at
com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionIntern
al(AbstractApplicationProxy.java:860)
at
com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(
LocalApplicationProxy.java:77)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseM
odel.java:755)
at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel
.java:717)
at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.j
ava:136)
at
com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.jav
a:335)
at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSessio
n.java:319)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(C
lientSession.java:713)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSessi
on.java:666)
at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250
at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:1
50)
at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.j
ava:62)
at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java
:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java
:401)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.j
ava:266)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java
:386)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java
:364)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalize
r.java:1039)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.pr
ocess(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFC_Fault_Exception: Fault
name: SERVICEKEY_INVALID, fault text: SERVICEKEY_INVALID
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1275)
at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)
at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:78)
at
com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)
at
com.sap.pcuigp.xssutils.menu.model.MenuLinksModel.hrxss_Ser_Getservicelink(MenuLinksModel.j
ava:237)
at
com.sap.pcuigp.xssutils.menu.model.Hrxss_Ser_Getservicelink_Input.doExecute(Hrxss_Ser_Getse
rvicelink_Input.java:137)
at
com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFC
ModelClassExecutable.java:92)
... 66 more

Hi
Check the return message from bapi,what's it showing??Before executing the bapi,put a breakpoint in r/3 system & check what values r getting passed to bapi..
U can check this in transaction se37,go to ur function module & put external break point over there.
OR
Execute BAPI through SAP GUI. if its execute properly do the following steps.
1. Do you have any mandatory input parameters?.
(check are you setting mandatory input parameters properly)
2. If they changed BAPI structure(data type) after model generation you have to model re-import model again.
Thanks

Activation of ODS fails: Change-Log Request ODSR_... does not exist in ODS

Hello Experts,
I have a problem loading in an ODS object in Release BW 3.5. This load is in parallel to loading in a Cube and InfoObjects from 10 different SAP sources monthly.
Everytime, I load data, Activation fails. The Error message is "Change-Log Request ODSR_... does not exist in ODS ..." These Requests (30 requests) are very old starting with the Go-Live date of the application in 2005. If I search for the first Request in Reconstruct, a request without a InfoPackage-Name is found and if I reconstruct the request, all other new loaded Request are activated and everything is fine. The next month, the same error appears, but without the one old request in the list reconstructed the month before of course.
A few months before I had to repair loading and deleted also requests in the ODS. Then I realized my mistake, that reconstruction is not possible, because the request was gone in the reconstruction list. So I searched for the PSA Request in the ODS reconstruction list, found the requests and reconstructed these. Could this be the reason for my current problem?
But how can I stop this error? Reconstructing all of the requests did not work, because one request says, no active update rules exist for this request. So I stopped reconstructing every request of the long list.
Please help me, I could not find any helpful information until now ...
Many thanks in advance,
Hannes

Hi,
For the old requests that you don't want and that are not valid, goto the monitor for those and mark them red. After that you won't face any problems while activating the new requests.
The reason this is happening is that during activation BW thinks that these old requests are valid as they are green and tries to activate them as they are in squence. When it dosen't find them then it gives the error. If you mark them red, they are ignored and the next request is taken into consideration.
Cheers,
Kedar

Table for the report RPUAUD00 Logged Changes in Infotype data

Hi
I have a query with the program RPUAUD00 Logged changes in Infotype Data. In which table stores the details of the program RPUAUD00. for example in the 1st period there is a LWP record for the employee. If in the 2nd period the LWP entered in 1st period has deleted, in the log the LWP displays for 1st period new field contents, Action Indicator I. The deleted information displayes in Old field contents with the Action Indicator D. We want to know in which table the LWP insert and LWP delete (d) details are stored.
This information required to create a report for ESI. In the report No of days (payroll processed for) has to mention. To know the no of days need to access the report RPUAUD00. From the RPUAUD00 the details of LWP insert and delete can be known.
Request to help in solving the issue
Thanks & Regards
EKP Yadav

Hello:
Logged changes in Infotype Data are stored in cluster table PCL4 ID LA and SA for employee and LB and SB for applicant. Maybe L is for longterm and S for shorterm
Cheers.
Antoine

Identify ODS change log request from Cube update rules init routine

Hello all.
I need to use a logic in the Start routine of a cube, whcih change log request are move from an ODS when doing a delta.
Anyone knows if this is possible???
Thnaks and best regards,
Alofnso.

Hello Oscar.
Basically my requirement is to do a selective deletion of the cube, before I load the new data, but the selective deletion has to be done according to some fields of the data that is going to be load to the cube.
That´s why I need this.
Best Regards,
Alfonso.

SEM-BPS 6.0 error message requested data cannot be locked but at 999 row?

Hi all,
We are using SEM-BPS with WIB and EP 7.0 and I encountered issues for the first time. I normally avoid configuring layouts with large hierarchies but at this one the client insisted. They are in testing right now and selection of relatively small node (approx. 10-20 cost centers) still gave us an error message.
I know layouts has a limit of 9,999 rows and we should have been okay since it is about 200-300 lines per cost center but we are getting the error message below and it mentioned a limit of 999 rows in the selection table.. Any way we can change that?
Thanks,
mary
Requested data cannot be locked (-> see long text)
Notification Number RSPLS092
Diagnosis
In order to edit data from InfoProvider 'ZYEE_C02', the requested data has to be locked exclusively for user 'YEESU01'. The data that is currently being requested is specified by a very large selection table. In order to lock the data exclusively, the system has to store a compressed version of this selection table on the SAP standard lock server. However, the compressed selection table still has more than 999 rows. So that a reasonable number of users are able to change data at the same time, the system limits the number of records allowed in a selection table to 999 records.
Information on Context of Lock Request:
Lock requests can come from BI-Planning or from BW-BPS. The context specifies the following information:
BI-Planning: for a lock request from a query, {Planning Function} for a lock request from a planning function.
BW-BPS: {Planning Area}{Planning Level}{Planning Package}{Planning Function}{Parameter Group}. For lock requests from manual planning the following is true: Planning function = '0-MP' and the parameter group is the technical name of the planning layout.
InfoProvider 'ZYEE_C02' is always a Basis InfoProvider. The current context information is:
'{0-ADHOC}{0-MP}'
System Response
The requested data cannot be locked.
Procedure
You can normally only avoid this by simplifying your selections. For more information, see the documentation on this.
Procedure for System Administration

Hi Mary,
in RSPLSE you use the option that the BI lock table is maintained in the SAP enqueue server. Here there is a limit - as explained in the long text of the message - that the compressed selection table for one enqueue request should not have more than 999 rows. This limit can not be changed.
The selection table seems to be very big, since the compression factor is at least 5. So please check your selection table:
1 check whether you can make the characteristic causing the problem not lock relevant
2 or use the second option that the BI lock table is maintained in a shared memory area of the central instance of the system.
But it is better to keep the selection tables small, e.g. by making some characteristics not lock relevant.
Check sizing note 928044, e.g. in case you want to use 2. The default setting is very small.
Regards,
Gregor

Change/Edit Request Attributes in CUP at Approval Stage

Hi All,
We have SAP GRC AE/CUP 5.3 SP07 installed in our environment. In our work flow of the request, there is a requirement that some of the request attributes need to be changed by the role owner/ approver at the approval stage of the request. The request contains both SAP standard as well as some custom attributes. I only see an option to edit the validity date or the roles/profiles of the request at the approval stage. Is this option configurable? If not, do we have any work around to achieve the requirement?
Thanks, Anil

Hi Harleen and Alpesh,
We are in GRC 5.3 SP8 and we would like to allow approvers in each stages to change the validity date (e.g. Valide to date) in a role request.   Here is the situation:
I have a workflow path which has two approval stages.   Both stages were configured to allow "Change Request Content".    What I noticed is the approver in the first approval stage can change the validity date and then approve the request.    But when the request is on the 2nd approval stage, the approver can no longer modify the validity date.
Is this the same scenario which Harleen said that "You cannot edit the information of a request once it enters the approval stages"?   If this is the same scenario, do you know whether a fix is considered by or available from SAP?
There may be situations where we don't want the 2nd approver to overwirte what 1st approver has approved.   However, in some situations we may want to keep that flexibility to let the later approver to have the last say.
Thanks for your input.

Change schedule line date

Dear All,
I have a requirement where required delivery date for one divisions material
in sale order and STO should automatically propose todays date plus 10 days i.e.
if any sale order or STO created today then required delivery date in STO and
SO should show 24.10.2010.
Accordingly we have maintained planned delivery time in material master 10 days in MRP2
view and it is working fine but another requirement is that user can reschedule the
delivery and he can change the schedule line date in So (RV45A-ETDAT) before or after
10 days in VA02 but it is not allowing to change it is considering todays date + 10 days.
In STO it is allowing for change the delivery date (MEPO1320-EEIND).
Plz advice how I can make the field RV45A-ETDAT changeable in sale order through VA02.
Regards,
sps.

Hello,
If you want a sales order to have the requested delivery date automatically populated with today's date +10 business days, this can be maintained via the following SPRO path:
SAP IMG --> Sales and Distribution --> Sales --> Sales Documents --> Sales Document Header --> Define Sales Document Types
Go into the sales document type you would like to maintain. In the section "Requested delivery date/pricing date/purchase order date", there is a field Lead Time in Days. Put 10 in here, and the requested delivery date will automatically be set to +10 days when an order is being created.
Planned delivery time in the material master is for when you're out of stock and the system proposes the next available delivery date. If you have stock on hand, when the availability check runs the system will use the line level delivery date. At order entry, when a line item created this line level delivery date is taken from the requested delivery date.
I hope this helps you.

Supply Side Change STO Delivery Date

Hello,
I apologize in advance as I suspect this has been asked somewhere, but the search terms are very generic...
Every implementation I've been at we've had the request to have the delivery date adjusted on STO's to match the actual availability of material in the supplying plant when known. Using Scheduling Agreements (LP or LU) I can get close to the desired functionality, but it's still not they are looking for.
Plant 1 orders 1000 EA a week for 10 weeks from Plant 2.
Plant 1 has MRP type P3 non-fixing with time fence, EX lot for lot buckets.
Plant 2 has MRP type P1 auto-fixing w/time fence, EX lot for lot buckets.
Running MRP generates the schedule lines in Plant 1 (source list with '2' in MRP field) which transfer demand to Plant 2 via special proc. key 40.
MRP creates P. req. in Plant 2 for supply from external vendor
Over time, some of the PO lines from the vendor get pushed out or pulled in. Using V_V2, we can adjust the deliveries as required, but we'd like to know if adjusting the delivery date on the vendor PO line items in Plant 2 can reschedule the schedule line on the STO/SA from Plant 1 so that their ATP for sales is always as accurate as possible.
SAP documentation implies that it can do this, but aside from checks on manually created items at the time of creation or change (existing POLI) there seems to be no option to do this, but instead the default requested date remains.
We're basically asking that the supply side drive the PO LI delivery date instead of the PO demanded date remaining firm.
I suspect confirmation control may bring some of that functionality, but we'd like to avoid that step of processing if there is a way.
thank you in advance.

Thanks for the quick reply. I'm not sure this completely solves the request, but the couple lines near the end on rescheduling infer the results we are looking for, but are not able to produce the results as explained by SAP. ATP works perfectly at creation time or change of the items mentioned, but the schedule line rescheduling seems not to work as expected.
I'll re-read with my SD team and make sure we're not missing something in the checks.
thanks again

Hi experts(I need one badi to copy the ECC to CRM request date forsales ord

Hi experts,
I am creating the sales order in ECC Va01 it is getting reflected in CRM (Crmd_order) transaction but when i am creating a Follow-up trans in that i am selecting sales option-->to OCM Quotation the request date at the header level is automatically changed to todays date so i want same date which is there in Va01 request date so please tell be the BADI which one i have to use.
Urgent requirement.
Thank you

I can use it but in that badi the date is same like Va01 request date (REQ_DATE_TZTF) so i cannot changed it i some the the date getting changed to todays date so please give the other badi which solves my problem

You have no authorization for the requested data

Hi Gurus,
While trying to display data in manual layout it shows the erros as
You have no authorization for the requested data.
Any reason behind that.
Thanks,
Debasish

Hi Debasisha
I faced the same problem yesterday, as Ivan told apply the transaction code rssm. In Business Information Warehouse Authorizations window go to checks for InfoProvider and select your Cube and click the change button. in that window you can see the which infoobjects are selected under switched on column deselct the checkboxes for authorization obj. save - refresh
and go to BPS screen execute your layout you can find your layout. I solved my problem like that.
Hope it helps you.
Regards,

Changing PR request date

Similar Messages

Maybe you are looking for