Run procedure for period

Hi all,
my need is to run procedure with one input parameter (date), for example
exec ZOO.PKG_Z60over.prepare(date '2012-01-27')1) this procedure accepts only 1 date, but I need period, for example
exec ZOO.PKG_Z60over.prepare(date '2012-01-27');
exec ZOO.PKG_Z60over.prepare(date '2012-01-28');
exec ZOO.PKG_Z60over.prepare(date '2012-01-29');2) my dates are stored in table calendar1, I'd like to select dates from table instead of typing
3) how do I run it without "exec" ?
Thanks ahead.

marco wrote:
Hi all,
my need is to run procedure with one input parameter (date), for example
exec ZOO.PKG_Z60over.prepare(date '2012-01-27')1) this procedure accepts only 1 date, but I need period, for example
exec ZOO.PKG_Z60over.prepare(date '2012-01-27');
exec ZOO.PKG_Z60over.prepare(date '2012-01-28');
exec ZOO.PKG_Z60over.prepare(date '2012-01-29');2) my dates are stored in table calendar1, I'd like to select dates from table instead of typing
3) how do I run it without "exec" ?
Thanks ahead.You can write a PL/SQL block like this where you will query the table calender and loop through it and call the procedure for each row.
begin
for i in (select <date_column> from calender1)
loop
ZOO.PKG_Z60over.prepare(i.<date_column>);
end loop;
end;
/

Similar Messages

Error while running procedure for refreshing AWS

Hello There,
I am using a procedure which consists the script of refreshing the analytic workspace. I call this procedure from Business objects data services for automatic refresh.
It used to work perfectly until the recent changes implemented.
The issue is, when I run the procedure the cube refreshes successfully. When the same procedure is called from BODS, it shows an error.
Error is :: XOQ-01601: error while loading data for cube dimension "BI_PETRA_DWH.ACTIVITY_TIME" into analytic workspace
Underlying DB error is : ORA-01858: a non -numeric character was found where a numeric was expected.
I dont get this error if I run procedure directly in SQL developer.
I verified attribues of dimension, there is only one numeric attribute and it is mapped to only numeric columns of view.
Can you please help me fixing this issue?
Thanks in advance.

Hello There,
I am using a procedure which consists the script of refreshing the analytic workspace. I call this procedure from Business objects data services for automatic refresh.
It used to work perfectly until the recent changes implemented.
The issue is, when I run the procedure the cube refreshes successfully. When the same procedure is called from BODS, it shows an error.
Error is :: XOQ-01601: error while loading data for cube dimension "BI_PETRA_DWH.ACTIVITY_TIME" into analytic workspace
Underlying DB error is : ORA-01858: a non -numeric character was found where a numeric was expected.
I dont get this error if I run procedure directly in SQL developer.
I verified attribues of dimension, there is only one numeric attribute and it is mapped to only numeric columns of view.
Can you please help me fixing this issue?
Thanks in advance.

Executing procedure for period

Hi all,
My need is to execute procedure with parameter date for period from 01.03.2011 till 31.03.2011.
One way is to type dates one per line:
EXEC schemename.pkg_name.procedure_name date '2011-03-01';
EXEC schemename.pkg_name.procedure_name date '2011-03-02';
EXEC schemename.pkg_name.procedure_name date '2011-03-30';
EXEC schemename.pkg_name.procedure_name date '2011-03-31';But how do I execute it using more simple code?

Hello
It kind of depends what you mean by simpler. If you want to avoid having 31 separate calls to the procedure listed on 31 lines, you can use a loop like so...
SQL> DECLARE
2
3      ldt_StartDate       DATE := TO_DATE('01/03/2011','dd/mm/yyyy');
4      ldt_EndDate         DATE := TO_DATE('31/03/2011','dd/mm/yyyy');
5
6 BEGIN
7
8      FOR lc_Dates IN (   SELECT
9                              ldt_StartDate + (rownum -1) dt
10                          FROM
11                              dual
12                          CONNECT BY
13                              LEVEL <= CEIL(ldt_EndDate - ldt_StartDate) + 1
14                      )
15      LOOP
16          dbms_output.put_line(lc_Dates.dt);
17      END LOOP;
18
19 END;
20 /
01-MAR-11
02-MAR-11
03-MAR-11
04-MAR-11
05-MAR-11
06-MAR-11
07-MAR-11
08-MAR-11
09-MAR-11
10-MAR-11
11-MAR-11
12-MAR-11
13-MAR-11
14-MAR-11
15-MAR-11
16-MAR-11
17-MAR-11
18-MAR-11
19-MAR-11
20-MAR-11
21-MAR-11
22-MAR-11
23-MAR-11
24-MAR-11
25-MAR-11
26-MAR-11
27-MAR-11
28-MAR-11
29-MAR-11
30-MAR-11
31-MAR-11
PL/SQL procedure successfully completed.HTH
David

Depreciation Run executed for a period but no posting found

Dear Experts,
I have checked a few of the FA in the Fixed Asset Master, and confirmed that they have not been depreciation run yet for period "2009-02". My current period is set to "2009-02" as well.
But when I tried to run depreciation run for "2009-02", I always get no posting.
What could have cause this problem?
Much Thanks in Advance!
Warmest Regards,
Chinho

Hi Chinho,
1, please make sure there is APC value for the asset. Means:
acquisition was created for the asset. You can check it from FA master data->document tab
Or the asset was imported into system with a APC value.
2, If the acquisition/import was done before current fiscal year, please make sure 'fiscal year change' to current fiscal year was done.
Regards,
Ivy Zhang
SAP Business One Forums Team

Depreciation run with special period

We require 2 set of FS reports:-
1.) FS as at 14/12/2007
2.) FS as at 31/12/2007
We have use the following period to derive the the reports
1.) Period 12 (Transactions 1st - 14th Dec 2007)
2.) Period 14 ( Transactions 15th - 31st Dec 2007)
Q1.)Should Dec depreciation run on period 14?
Q2.) If yes, will the depreciation run capture the depreciation from 1st - 31st Dec 2007?
Q3.) We have tried to run Dec depreciation in period 14 but error "According to the posting cycle, you should post period 012 next."
Pls advise
1.) Steps to run Dec 2007 depreciation in order to capture the whole month depreciation.
2.) Which period to open in OB52.
Kindly assist as this is urgent. Points will be rewarded. Thank you

Dear Hari,
Thank you for the helpful points. Rewarded.
FYI, our cut off date is 14th Dec 2007. Any transactions after this date will go to period 14. In OB52, we set only period 14 open to block user from posting to other periods. Will this affect the depreciation run (given scenario where we run AFAB for period 12)?
When we run AFAB for period 12, this is the error we get:
Period 12 is not allowed
Message no. F5567
Diagnosis
The period entered (12) is different from the period calculated (14) and is also not in the interval for special periods (013 to 016).
System Response
Error.
Procedure
Correct the value entered for the posting period.
What shoud we do?

WORK FLOW & PROCEDURE FOR FOR SNP CAPACITY LEVELLING HEURISTICS RUN

Dear Sir / Madam,
Currently, we are taking only SNP Heuristics Run and the output viz. planned stock transfer requisitions are being passed to PPDS as such. But now we feel, SNP capacity leveling can play a vital role in getting more fine tuned results from PPDS. So, We wants to start using the SNP Capacity leveling run. We shall like to know the work flow / procedure for taking the SNP capacity level run i.e. what inputs should be properly reviewed before taking the SNP capacity level run and what shall be its output..? Kindly let us know the procedure / work flow for taking the SNP Capacity Levelling Run.
Your early reply in this regard shall be really appreciable.
Thanks & Best Regards,
Sanjeev Chugh
25-Mar-10

Hi Sanjeev,
as in any other module, correct master will play a key role in getting effective results in capacity levelling. you will need to check the following master data while setting the system for capacity levelling :
Consistency in BOM in R/3 and PPM/PDS
Consistency in Routing in R/3 and PPM/PDS - the actual through put on the shop floor should be the same as that in the routing and in the PPM/PDS. unless this is in sync, no amount of levelling can return good results.
Maintenance of shift - again as present in the shop floor.
you can provide the dump of the above master data and ask the shop floor engineers to validate the data as it exists in the ssytem. you can do the consistency check between R/3 and APO yourself using queries. Once they have validated this master data and the the actual master data reflects in your system, i think, the job is more than 50 % complete.
also you need to check the lot sizes, rounding profiles, and period factor, becasue all three combined play a major role in giving good or better results after levelling.
you may also check at what level you want to run the levelling. whther the bottleneck is at the finished component level, or 2nd level, etc. you may check whther you have discrete manufacuring or REM and if you really want to levelling on REM order.
then you need to analyse, what is the lengh of horizon you want to run the capacity leveling on. sometimes it makes no sense to run on the entire horizon because if capcities are already overlaoded, you will not achieve the desired results.
hence depending upon the level of your understanding and comfort of the planner (who will be using this result), the horizon can be increased grdually.
if you are starting to implemement capcity levelling, you can sumulate runs and show the results to the planner and check if the standard capacity heursitics satisfies their requirement. else you can go for custom requirement.
you will also have to decide on the stratagies, priorities,etc based on the business requirement.
i think the above should give some starting direction to implement capcaity levelling in your system.
award points if you find this useful.
Rgds, Sandeep
Edited by: Sandeep Budhiraja on Mar 25, 2010 11:49 AM

Stored procedure for getting host name, host instance and status of that host is it running or stopped.

Hello all,
yesterday I got one task in that I have to stored procedure for getting host name, host instance and status of that host is it running or stopped.
any body knows where exactly, In which table this details are there in BizTalk databases.
thanks

Status of the host instance is not stored in the SQL database for you to query the status using stored procedure. You have to either use Powershell or WMI to get the status.
In SQL, following table contains the details about the host like Name, LoginName, IsDisables etc but status of the host instance is not stored in the database.
SELECT * FROM BizTalkMgmtDb..adm_HostInstance
Powershell to get the status:
http://axonolympus.nl/?page_id=186&post_id=969&cat_id=6&lang=en
WMI to get the status:
https://msdn.microsoft.com/en-us/library/aa561820.aspx?f=255&MSPPError=-2147217396
https://msdn.microsoft.com/en-us/library/aa578621.aspx
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

For OS X: Whenever I have internet access my disk is running continuously for a period of time without any activity on my part. When I close internet access the disk activity stops. Who is fishing for data?

For OS X v5 or 6: Whenever I have internet access my disk is running continuously for a period of time without any activity on my part. When I close internet access the disk activity stops. Who is fishing for data?

Thanks for your reply. I don't use itunes so that couldn't be it. Reading about Little Snitch and Hands Off, however, educated me about the data harvesting in many apps and that when buying from the AppStore one will more likely get Apps with benign data harvesting.

Posting run request for future period; check your entry message no.AA697

Hello Guru's,
I have below error while Depreciation run in T.Code AFAB
"Posting run requested for future period; check your entry" message no.AA697
Request help
thanks in advance
Regards
Chintamani

Hello Chintamani,
Why you want to post the depreciation for future period?
Is the future fiscal year in open or is the posting period open for that? If no, please open that period with AJRW T code if you want to post the depreciation for future period but it is not recommendable.
Check the posting period once again because the given posting period belongs to future year? So please do re-chk and give correct period according to your current fiscal year.
You can get your fiscal year details and assignment of fiscal year variant to the co,code details in OB29 and OB37 t codes respectfully.
Check the OSS Note: 1150235 - Preventing depreciation posting run for future
I hope it helps else revert us with your query.
Thanks & Regards,
Lakshmi S

Depreciation Posting Run for Period 02 in 2008

Dear All,
I have closed the 2007 fiscal year for fixed assets and executed the fiscal year change successfully. I have also executed the depreciation run for January period 01 without any errors, however, when I attempted to execute the depreciation run for February (period 01), I keep on getting this error message:
_Test run was terminated. No documents were created in this run_
Upon further investigation, I got this long text for the error message:
In the number range interval for the document type for posting depreciation, a document has been posted which was not created within the framework of depreciation posting. The last document posted by depreciation posting was assigned the number.
I have checked my number ranges and there is really no problem there.
Can somebody please help me as we need to close the financial books for period 02 and would not be able to do this until the completion of depreciation run.
Thank you in advance for your kind assistance

Check first wht is the posting period varient assign and than check all the assignments...including the number ranges and document types.
than try to run it again
hope it works
Edited by: sejal singh on Mar 18, 2008 11:12 AM

Depreciation run For Period 2

Dear All,
Currently am configuring a simple scenario of asset configuration fop book depreciation
i have done the depreciation run ( Both Test Run & Back ground Processing ) for the period 1 and the posting was done successfully
when i went for the depreciation run for the 2nd period no documents are generated ( Tried Test Run ) and no error message is displayed
Can any one help me solving this issue
Regards
Arun.R

Run the report in test mode without Error Analysis and List assets on.
When this not helps look to your asset if there is plaaned depreciation for period 2

Run Forecast for previuse period

We have certain materials with MRP type VM and want to run forecast first The Period Indicator is M (month).
When user press the run Forecast button, a pop up screen periods appears and you should select a current period 8.2007 or next 9.2007 to run a forecast but for testing AND Due to business requirements, we upload consumption and open PO till 31-5 so we need to run forecast for 6.2007 period to compare values with legacy system before going life.

Hello Chintamani,
Why you want to post the depreciation for future period?
Is the future fiscal year in open or is the posting period open for that? If no, please open that period with AJRW T code if you want to post the depreciation for future period but it is not recommendable.
Check the posting period once again because the given posting period belongs to future year? So please do re-chk and give correct period according to your current fiscal year.
You can get your fiscal year details and assignment of fiscal year variant to the co,code details in OB29 and OB37 t codes respectfully.
Check the OSS Note: 1150235 - Preventing depreciation posting run for future
I hope it helps else revert us with your query.
Thanks & Regards,
Lakshmi S

Creating wrapper procedures for Long running procedures

In SQL server, we can create a wrapper procedure to call long running procedure. Wrapper procedure calls long running procedure and returns to its calling application and give message "your request has been received and being processed. result will sent to your email-id." So user need not wait for complete execution for his request. From long running stored procedure we can send email to user stating all execution result he wants.
Is there any way to implement it in Oracle9i? Or any other technique to call such long running procedures asynchronously through wrapper procedure sothat user need not to wait and also avoid "request time out" error.

This question would be better off posed in the Oracle Data Provider for .NET forum.
Christian

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Column link in interactive report to run procedure and refresh

I have an interactive report which displays a report based on a table. This is a summary table populated overnight from some complex spatial analysis, which takes a few hours to run. I have a requirement to allow the user to refresh one row in this table - they would do this during the day if they needed to see the most up-to-date values.
I have a package with two stored procedures - one which does the full refresh of the table, and one which refreshes one row when PK is passed in.
One of the columns in the table is 'last_refreshed' which is a date - this is shown in the interactive report including minutes.
I was thinking that maybe I could include a hyperlink on this 'last_refreshed' date column in the report. When a user clicked on it, it would run the stored procedure for that row and would refresh the report.
Any ideas on how I could do this? I've hit a bit of a dead end for now.
Thanks

OK, I worked it out.
I created an application item to store a global variable.
Then in the column attributes of the report, I set the 'last_refreshed' to be a linked column, setting target to the current page and then setting the application item global variable to be the row PK.
Then I have a Process which runs the required stored procedure reading the application item global variable, set to run on page load.
Sorted.

Run procedure for period

Similar Messages

Maybe you are looking for