Use of parameter IDOC_OPENED_FLAG in FM IDOC_STATUS_WRITE_TO_DATABASE

Hello Friends,
I am using the FM IDOC_STATUS_WRITE_TO_DATABASE to set the IDOC status .
I just wanted to know wat is the significance of the paramter IDOC_OPENED_FLAG.
If I set it and process I am getting an error "IDOC NOT OPENED".
If I dont set it The processing is fine , But i want to know the importance of this flag and its influence on the FM.
Comradely,
K.Sibi

HI Sibi
When ever you want to add a Status to existing records
First you need follow the below steps...
Step 1: EDI_DOCUMENT_OPEN_FOR_PROCESS
Step 2: <process will take place to add status record..Fm EDI_STATUS_ADD_BLOCK >>
Step 3: EDI_DOCUMENT_CLOSE_PROCESS
IN FM IDOC_STATUS_WRITE_TO_DATABASE IF YOU SET
IDOC_OPENED_FLAG is Flagged i.e. set 'X'.
THEN YOU can add the status records to IDocs...directly
Note: Before you add the IDoc status... you need to use EDI_DOCUMENT_OPEN_FOR_PROCESS to open the document to add the status
After adding the status records using IDOC_STATUS_WRITE_TO_DATABASE (IDOC_OPENED_FLAG is Flagged i.e. set 'X') then
You need to use FM EDI_DOCUMENT_CLOSE_PROCESS to close the document....
Direct question to Answer:
EDI_DOCUMENT_OPEN_FOR_PROCESS & EDI_DOCUMENT_CLOSE_PROCESS wonu2019t be happen in Fm IDOC_STATUS_WRITE_TO_DATABASE IF YOU SET IDOC_OPENED_FLAG is flagged
Thanks
Ramesh

Similar Messages

How to use lexical parameter in report

i want to use lexical parameter in report and pass parameter from form how it is possible in detail
A.R

Hi,
typically you fill your lexical paramter in the after-paramform-trigger out of the values of your bind-parameters (giving end users directly control over lexical parameters might not be a good idea). Inside PL/SQL a lexical parameter is referenced like bind parameters with ":". In the query it's referenced via "&" and represents a part of the query.
A simple example.
- p_deptno as bind parameter
- p_where as lexical paramter
- end user choose value for p_deptno (10,20,... or nothing)
- Trigger: if :p_deptno is not null then
:p_where := 'WHERE deptno = :p_deptno'
else
:p_where := null;
end if;
- Query select ... from emp &p_where
Regards
Rainer

How to use import parameter to be instead of SQL where sub-sentence ?

I wrote a RFC to read data from SAP table. To fetch data flexibility, I want to use import parameter xx instead of where sub-sentence in SQL sentence.
   For example, "SELECT * FROM T WHERE XXX", and "XXX" is a importing parameter.
   How can I use it.
   Thanks a lot.
   Frank.

FUNCTION ZRFC_04.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(TARGETTABLE) LIKE MAKT-MAKTX
*"     VALUE(TWHERE) LIKE MAKT-MAKTX
*" EXPORTING
*"     VALUE(ZRETURN) LIKE MAKT-MAKTX
*" TABLES
*"      TMP_TEST1 STRUCTURE ZTEST1
DATA:
TRANSACTION_ID LIKE ARFCTID,
V_VAILD(1) TYPE C,
scond(80) TYPE c.
V_VAILD = 'X'.
GET PARAMETER twhere fields scond.
The error " 'LATE FIELDS' expected, not 'TWHERE FIELDS' " generated.

Want to use one parameter of first command into second parameter.

Hi, Experts,
Please help me out I am stuck in a crystal report. Actually i have written two commands in crystal report.
first one is as follows:-
Select * from oinv T0 inner join inv1 T1 on T0.DocEntry = T1.DocEntry Where T0.DocNum = {?Invoice No}
Second One is as follows:-
Select * from ibt1_Link Where BaseNum = {?Invoice No}
What i want is I am passing Parameter in both Command Which took Invoice no as an input, So i don't want to input ttwo parameter both for invoice no. can i use first parameter in my second command or not. If Yes then please tell me.How can i do the same.
Regards
Hanes

Have you tried joining your commands on the basenum = docnum fields? That should filter the second command?

How to use a parameter field value as a substring in a "like" statement?

Hi all,
I'm trying to use a parameter field in a Record selection formula where the parameter field value would be a substring of the data stored in the field.
My parameter field (SlctResearcher) is constructed as follows:
Type: string
List of Values: static
Value Field: (Reports) RptAuthors
(in Value Options) Allow custom values?: True
{Reports.PubDate} in DateTime (2009, 04, 01, 00, 00, 00) to DateTime (2010, 03, 31, 23, 59, 59) and
{Reports.RptAuthors} like "*{?SlctResearcher}*"
When I hit F5 to generate the data, I get no results (and the parameter prompt field does not even come up...)
If I modify the formula to put a hard-coded string, like
"*Jones*"
after the 'like', I get results (all the reports where "Jones" is a substring in the RptAuthors string.) If I modify the formula to just use the parameter field without the quotes/stars like:
{Reports.PubDate} in DateTime (2009, 04, 01, 00, 00, 00) to DateTime (2010, 03, 31, 23, 59, 59) and
{Reports.RptAuthors} like {?SlctResearcher}
I do get the parameter prompt field, but still no results even if I put in a valid substring value (since it is not searching for a substring anymore...)
How can I do this?
Thanks,
Will

1st thing... Make a copy of your report before doing anything!!!
To use a SQL Command, you'll want to open the Database Expert and look at the Current Connections. Expand the data source and the 1st option you see is the Add Command option.
To find the SQL That CR is currently using, choose Database from the menu bar and select Show SQL Query...
You can copy this and paste it directly into the command window. (If you you can write your own SQL you don't need copy CR's, it's just an option.)
You'll also want to take not of any parameters that you have, you'll need to add them the the Parameter List of the command as well... be sure to spell them EXACTLY as they are in the design pane.
Anyway, once the SQL statement is in the Command window you'll be able to alter the WHERE clause to use the wild cards.
For future reference... What type of database are you reporting against???
Jason

HR ABAP: Issue with using 'nocommit' parameter on FM HR_INFOTYPE_OPERATION

Issue with using nocommit parameter on FM HR_INFOTYPE_OPERATION:
My client has a requirement to create the following 4 infotypes in sequence in a LUW, i.e either all are created or none is created.
9045 (custom infotype)
0045
0078
0015
I tried to use the nocommit parameter on FM HR_INFOTYPE_OPERATION to insert the 4 infotypes
in a nocoomit mode and then at the end I have issued
'Commit Work', but to my surprise only I/T 0015 is created in the database and the first three (9045, 0045 and 0078) did not make it to database.
I searched many threads on SDN but could not find a solution.
Please let me know if there could be any solution to implement the LUW.
YOur inputs will be appreciated.

Hi ,
i think u can also try with this FM HR_MAINTAIN_MASTERDATA , see its documentations.
no commit works like a simulation mode , what u can do is ,
call FM for all Infotypes and collect all error msgs if any , then finally call FM for all infotypes again without passing nocommit work ( i.e space).
regards
prabhu

Use of parameter sets with prepared INSERTS via Oracle's ODBC driver 8.1.6.4

Oracles ODBC driver, version 8.1.6.4, allows for driver configuration of three different batch auto commit modes. If I select COMMIT ALL SUCCESSFUL STATEMENTS and cause my app to execute a prepared and parameterized INSERT statement that makes use of parameter value sets, all records up to the first record that causes an error are committed. What is happening? The driver returns only one diagnostic record, with SQLGetDiagField returning the index of the bad record through the [SQL_DIAG_ROW_COUNT] field. Regardless of whether SQLExecute executed successfully or not, the [SQL_ATTR_PARAM_OPERATION_PTR]/ [SQL_ATTR_PARAM_STATUS_PTR] buffers are not initialized by the driver. Even more so, the drive returns SQL_PARC_NO_BATCH for SQLGetInfo when [SQL_PARAM_ARRAY_ROW_COUNTS] is passed. Does anyone know if the driver fully or partially or does not support use of parameter value sets. If it is only partial implementation, ignoring the parameter operation and status buffers, in my opinion, greatly diminishes any real use of parameter value sets. Does anyone known if the above problems disappear with use of Oracles ODBC driver, version 8.1.7.3.0?
All help is greatly appreciated,
Chris Simms
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Justin Cave ([email protected]):
What version of the database do you have on the back end?
Justin<HR></BLOCKQUOTE>
Oracle8i version 8.1.6. Looking at the specs that come with the ODBC driver upgrades, version 8.1.7.3.0 [which requires Oracle*i version 8.1.7] and 8.1.6.4, it seems that similar enhancements/fixes were made to both. I honestly do not know if what I am attempting is possible with either of the ODBC drivers. I really would prefer not to have to drop down to programming using OCI.
Chris
null

Getting error when using the "/parameter" switch in command line run

Has anyone experienced this problem before?
My report queries over 100,000 records from a view. When the report is run from the command line every thing works fine.
But when I add a condition using a "parameter", although the report still runs fine from the destop, when launched from the command line it errs.
"Oracle Discoverer Desktop has encountered a problem and needs to close. ..."
"The instruction at "0x0044397c" referenced memory at "0x0000004e". The memory cound not be "read"...."
I'm guessing its a memory issue with my PC. I've tested using a parameter with other reports using fewer records and it doesn't err from the command line.
I can work around the issue by not using a parameter but then I have 20 versions of the same report each with a different condition.
Any suggestions would be appreciated.
Lise McGillis

Hi Michael,
I'm using an DELL Intel Pentium 4 CPU 3.00 GHz with 1 GB of RAM. We use Microsoft Windows XP Prof version 2002.
As for Discoverer we are using 10G, Desktop Client 10.1.2.48.18 - 1047500 KB available memory , 2099744 KB Free disk space.
I'm not sure I have acess to a computer with more RAM but I'm looking into it.
What I'm frustrated by is the fact that the parameter works fine when run directly from the desktop but when passed from the command line it bombs... but only when dealing with mega records.
Lise.

How to use a parameter of a report program from selection screen in a dialog program

how to use a parameter value(entered ) of a report program from a selection screen in a dialog program.
I have to fetch the value entered in the parameter of report program and display it in a dialog program

Hi Aasim,
Just mention like below in your ABAP report.
PARAMETERS: p_aufnr TYPE aufnr MEMORY ID ord.
and mention the same memory ID name in the module pool screen property it automatically populates the value to and fro

How to use a parameter of a report program in a dialog program

how to use a parameter of a report program in a dialog program.
I have to fetch the value entered in the parameter of report program and display it in a dialog program

Hi Aasim,
Just mention like below in your ABAP report.
PARAMETERS: p_aufnr TYPE aufnr MEMORY ID ord.
and mention the same memory ID name in the module pool screen property it automatically populates the value to and fro

Bug while using string parameter values in postgresql query

Hi,
I have the following query for the postgresql database:
Code:
<queryString><![CDATA[SELECT
evt_src_mgr_rpt_v."evt_src_mgr_name" AS esm_name,
evt_src_collector_rpt_v."evt_src_collector_name" AS collector_name,
evt_src_grp_rpt_v."evt_src_grp_name" AS grp_name,
evt_src_grp_rpt_v."state_ind" AS state_ind,
evt_src_rpt_v."evt_src_name" AS src_name,
evt_src_rpt_v."date_modified" AS date_modified,
evt_src_rpt_v."date_created" AS date_created,
CASE WHEN $P{mysortfield} = 'evt_src_mgr_name' THEN evt_src_mgr_name
WHEN $P{mysortfield} = 'evt_src_collector_name' THEN evt_src_collector_name
WHEN $P{mysortfield} = 'evt_src_grp_name' THEN evt_src_grp_name
ELSE evt_src_name END as sort
FROM
"evt_src_mgr_rpt_v" evt_src_mgr_rpt_v
LEFT JOIN
"evt_src_collector_rpt_v" evt_src_collector_rpt_v
ON EVT_SRC_MGR_RPT_V."evt_src_mgr_id" = evt_src_collector_rpt_v."evt_src_mgr_id"
LEFT JOIN
"evt_src_grp_rpt_v" evt_src_grp_rpt_v
ON evt_src_collector_rpt_v."evt_src_collector_id" = evt_src_grp_rpt_v."evt_src_collector_id"
LEFT JOIN
"evt_src_rpt_v" evt_src_rpt_v
ON evt_src_grp_rpt_v."evt_src_grp_id" = evt_src_rpt_v."evt_src_grp_id"
LEFT JOIN
"evt_src_offset_rpt_v" evt_src_offset_rpt_v
ON evt_src_rpt_v."evt_src_id" = evt_src_offset_rpt_v."evt_src_id"
WHERE
$P!{mysortfield} LIKE '$P!{searchvalue}' || '%']]></queryString>
That is I try to select only the records where the field which is
selected by user as report parameter ($P{mysortfield}) contains data
starting with the text entered by user as a report parameter
($P{searchvalue}).
When I try to run the report in iReport with active connection to the
database the report is generated as expected.
But when I try to run the report from Sentinel Log Manager I get the
following error: "java.lang.String cannot be cast to
net.sf.jasperreports.engine.JRValueParameter".
After several detailed debug sessions I finally came into a conclusion
that this error is related to the use of parameter values (
$P!{mysortfield} and $P!{searchvalue} ).
I even tried using the following WHERE clause (which emulates the
queries as used in standart reports (especially at VendorProduct related
SQL queries ) with no success:
Code:
WHERE
($P{mysortfield} = 'evt_src_mgr_name' AND evt_src_mgr_name LIKE ($P{searchvalue} || '%')) OR
($P{mysortfield} = 'evt_src_collector_name' AND evt_src_collector_name LIKE ($P{searchvalue} || '%')) OR
($P{mysortfield} = 'evt_src_grp_name' AND evt_src_grp_name LIKE ($P{searchvalue} || '%')) OR
($P{mysortfield} = 'evt_src_name' AND evt_src_name LIKE ($P{searchvalue} || '%'))
Any suggestions?
hkalyoncu
hkalyoncu's Profile: http://forums.novell.com/member.php?userid=63527
View this thread: http://forums.novell.com/showthread.php?t=450687

bweiner12345;2167651 Wrote:
> I'm not 100% sure the $P! (instead of just $P) is needed in that WHERE
> portion of your SQL statement.
>
> What I would suggest doing is building the WHERE portion of your query
> up again step by step. That is, instead of using any parameters in your
> WHERE:
>
> $P!{mysortfield} LIKE '$P!{searchvalue}' || '%'
>
> ... take a step back and literally hard-code some values in there, such
> as:
>
> evt_src_mgr_name LIKE '%' || '%'
>
> ... and run it on your box to make sure it works fine.
>
> If it works fine, start substituting the parameters one by one:
>
> $P{mysortfield} LIKE '%' || '%'
>
> .... test on the box.
>
> $P{mysortfield} LIKE '$P{searchvalue}' || '%'
>
> .... test on the box.
>
> It may be a little tedious, but at least you'll find out where the
> problem is occurring... and may be quicker in the long run.
>
> (Note: In my above example steps I didn't use the ! in with the
> parameters, as I don't think they are needed in the WHERE clause... but
> I could be wrong... and by following the above step-by-step technique
> should answer that for sure.)
Thank you for the suggestions:
While trying to implement your suggestions I realized that there was a
error at the parameter name I used inside the where clause (it should be
$P{searchfield}).
Here are my results:
Code:
vt_src_mgr_name LIKE '%' || '%'
worked as expected.
Code:
$P{searchfield} LIKE '%' || '%'
produced PDF but wrong output.
Code:
$P!{searchfield} LIKE '%' || '%'
resulted with the error "java.lang.String cannot be cast to
net.sf.jasperreports.engine.JRValueParameter" and no PDF.
Then I tried the following where clause which resulted in exactly as
expected PDF:
Code:
WHERE
($P{searchfield} = 'evt_src_mgr_name' AND evt_src_mgr_name LIKE ($P{searchvalue} || '%')) OR
($P{searchfield} = 'evt_src_collector_name' AND evt_src_collector_name LIKE ($P{searchvalue} || '%')) OR
($P{searchfield} = 'evt_src_grp_name' AND evt_src_grp_name LIKE ($P{searchvalue} || '%')) OR
($P{searchfield} = 'evt_src_name' AND evt_src_name LIKE ($P{searchvalue} || '%'))
As a summary:
* The query which works in iRepord do not work in Sentinel Log
Manager.
* I found a workaround for my case.
* I did not checked, but the reports provided in Sentinel RD which use
the same technique for VendorProduct parameter (i.e. the reports with
query string containing
Code:
LIKE ($P{VendorProduct} || '%')
will most probably not work as expected IF Sentinel RD uses the same
code as Sentinel Log Manager.
hkalyoncu
hkalyoncu's Profile: http://forums.novell.com/member.php?userid=63527
View this thread: http://forums.novell.com/showthread.php?t=450687

URL iView Problem - How to Use URL Parameter of Type 'User Information'

Hello URL iView experts
I am currently working on integration of backend-functionality with the help of an URL iView.
I want to use a parameter of type 'User Information'. In SAP Help Library it is said, that it is possible to set the value of a parameter according to a dynamic query on the users attributes. (Link SAP HELP)
It is also said, that one can retrieve the Logon ID of the users account.(Attribute Name: j_user -> Link SAP HELP Attributes )
I can choose the type 'User Information' but i don't know what to specify in the field 'Value'.
I have made a screenshot of the problem.->[Link to screenshot|http://img66.imageshack.us/img66/7782/urliviewproblemfrsdnthrel3.jpg]
But if i am calling the application this way, he doesn't retrieve the Logon-ID of the account, but he just uses the 'j_user' as value for the parameter.
Can you tell me, what i need to specify in the field value?
Best Regards
Marcus
Edited by: Marcus Böhm on Jun 2, 2008 1:22 PM

Hi Marcus,
> It is also said, that one can retrieve the Logon ID of the users account
This is not correct; on the help.sap.com-page concerning the URL-iView-Parameters, it is printed that "other attributes (general, account, group, role) are not supported". The j_user attribute is part of the account group, so - not supported.
For your needs, it may be a better choose to use the AppIntegrator, which offers such a possibility by using "<User.LogonUid>"; see http://help.sap.com/saphelp_nw70/helpdata/EN/36/5e3842134bad04e10000000a1550b0/frameset.htm and https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0cbc309-ff89-2a10-8bad-bcde4c152ecb
Hope it helps
Detlev

How can i make calculation in two file using two parameter

how can i make calculation in two file using two parameter
Solved!
Go to Solution.

i am having two differnt file, both file having no and time , i want to make programme that when, number and tiome is same in both file give that index onle in , i am going to attached the file
Attachments:
iisc11-jan2010extract.txt ‏1253 KB
sp3.xlsx ‏12 KB

Using paramform parameter !!!

Dear all,
I would to know, where can i specify the paramform parameter in the sample code delivers with the package:"Oracle Forms Services - Using Run_Report_Object to call Reports with a Parameter Form".
It's a set of document and sample codes which gives a solution encountred when we try call Report from Form using a parameter form.
Thank u for your help.

I just implemented the white paper's RUN_REPORT_OBJECT_PROC procedure yesterday. (We're doing a simple pilot 6i Client Server form/report conversion to Forms10g and 10gAS.)
To be honest, after reading the white paper I wasn't quite sure what this procedure was going to do. But after implementing it, here's what we see:
If we pass a PARAMFORM=YES to the procedure using the report_otherparam, an HTML representation of the report's parameter form will be generated for the user.
In our case, the original report parameter form had a populated list box of payroll periods. The new HTML parameter form even used the boilerplate text from our original parameter form and had a populated list box of the payroll periods. So it basically duplicated the original client/server parameter form into HTML with no work needed from us. I was impressed.
Our only problem at this point is that when calling the report from our webform, we're being asked for a single signon logon. We don't want to use that yet, but can't find where to turn it off.
Dave

HOW TO USE LEXICAL PARAMETER IN FORMS9I

CAN I USE LEXICAL PARAMETER IN FORMS9I I WANT TO CREATE QUERY LIKE THIS
SELECT * FROM &TABLE_NAME
WHERE &CHOICE
WHERE &TABLE_NAME = EMP, AND &CHOICE EMPNO=12344
PLS HELP

No, you can do it in sqlplus or reports but not in forms.
If this is a datablock query you need to use set_block_property.
If it is in a trigger you need to use execute immediate.

Use of parameter IDOC_OPENED_FLAG in FM IDOC_STATUS_WRITE_TO_DATABASE

Similar Messages

Maybe you are looking for