Value Type and Report Type in Report Painter Report

Is there a way I can get both characteristics WRTPP and RRCTY in one table? Or, can I work with two different tables in creating Report Painter report? I need to get the planned values of cost elements with record type 1 and value type 10 to show under one column in my report.
Your help is very much appreciated.
Edited by: Mauricio Villa on Oct 23, 2010 10:32 PM

use the selection criteria to restrict the field types in the query designer- use other variables to check the value
if it doesnt reconcile- you can alternatively use a multi provider for the same thing- that way you will get the same amount in 1 column and you could restrict using the infoprovider column

Similar Messages

TPM12 Report not shwoing Product Type and Product Type Text

Hi ,
After we went live with a upgrade the report TPM12 which is run by the Treasury department every day, is now showing the blank values for "Product Type", "Product Type Text", "Transaction Type", and "Transaction Type Text".
Which was not the case earlier.
Any adivce please.
Thanks,
Venkat

Good day
We have a similar issue.
In our system the line item type for the CW product was IDCW. When we however split them by batch into two sub-lines, the new lines defaulted to IDLV (instead of the expected IDCW).
So I think Alexander's diagnosis is spot on?
My question though... What logic does EWM use to derive the item type for the sub-lines? Because surely it should be the same as the 'parent' line item (IDCW in the case) ?
Please advise
Callie

Is there any standard ODS for Contract (value type and quantity type)?

We know that in MM, contract records can be categorized into two different categories, Value type and Quantiy type. We are trying to see if there is any Contract ODS in business content that we can install which can take care of these two types of contract records that we can bring them over to BW from R3?
Thanks

Hi Kevin,
Please see this link,ODS looks related to your requirement.But seems its for CRM and not for MM.
http://help.sap.com/saphelp_nw04/helpdata/en/38/c3813ed9d23e44e10000000a114084/frameset.htm
cheers,
Vishvesh

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

Definition of Message Type and Transaction Type from the Implementation per

My assumption is that both, Notification Type and Message Types are same.
Is the above assumption right?
In Sol Man 4.0, the notification types required are
1) ABSC 2) SLF1 3) TASK
Are there any other notification types required for Sol Man 4.0?
The main transaction types required in Sol Man 4.0 are
SLFI, SLFT and SLFN
What is the significance of External Number range and Internal Number range used in the transaction type?

Hi
1 > A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
The characteristic of columns and variables that defines what types of data values they can store. Examples include character, floating point and integer
Check out the details:
http://en.wikipedia.org/wiki/Data_type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
details:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
2) Regarding the difference between XI 3.0 and PI 7.0, this threads will clear your doubts:
difference between XI 3.0 and P.I 7.0
Difference/ changes from XI 3.0 to PI 7.0
Regard's
Chetan Ahuja

How could I retrieve metadata about Array Type and Table Type?

I use DatabaseMetaData.getUDTs() method for obtain metadata about Object Types, but this method doesn't work with Array Type and Table Type.

JJ,
Go into the diagrams of the DBTools List Columns and DBTools Get Properties respectively. When you inspect this diagram, you will see the raw ActiveX properties and methods called to get the size information. The value of -1 means the requested recordset is already closed. This is the sort of thing that is controled by the driver (ODBC, OLE DB, Jet, etc) you are using. Notice that you can right click on the property and invoke nodes and get more information about these specific items directly from the ADO online help.
Crystal

Help in using record type and object type

Hi Experts,
I am new to object types and record types.
I want to return the output of this query using one OUT parameter
from the procedure using RECORD type or OBJECT type.
with out using refcursor.
SELECT empno,ename,sal FROM emp WHERE deptno=30;
Let us assume the query is returning 50 records.
I want to send those 50 records to OUT parameter using record type or object type.
Please provide the for the requirement code using RECORD TYPE and OBJECT TYPE separately.
Your earliest response is appreciated.
Thanks in advance.

Hi All,
I have tried this.But it ising not work
CREATE OR REPLACE PACKAGE maultiplevalues_pkg
IS
TYPE t_record IS RECORD
(empno emp.empno%TYPE,
ename emp.ename%TYPE,
sal emp.sal%TYPE);
V_RECORD t_record;
TYPE t_type IS TABLE OF V_RECORD%TYPE;
PROCEDURE maultiplevalues_pROC(p_deptno IN emp.deptno%TYPE,
dept_result OUT t_type);
END;
CREATE OR REPLACE PACKAGE body maultiplevalues_pkg
IS
PROCEDURE maultiplevalues_pROC(p_deptno IN emp.deptno%TYPE,
dept_result OUT t_type)
is
begin
dept_result :=t_type();
for I in(
select EMPNO,ENAME,SAL from EMP WHERE deptno=p_deptno
LOOP
dept_result.extend;
dept_result(i).empno :=i.empno;
dept_result(i).ename :=i.ename;
dept_result(i).sal :=i.sal;
END LOOP;
END;
END;
Please help me OUT return multiple values through single OUT variable in a procedure.
Thanks.

Difference between line type and table type

hi,
can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

hi,
Go through this blog, this might help you.
/people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
 "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
In a BSP when we need to work with a table we must always do the following:
1, in the Types definitions create a structure:
 types : begin of ts_reclist,
mso-bidi- style='mso-tab-count:2'> receiver type somlreci1-receiver,
mso-bidi- style='mso-tab-count:2'> style='mso-tab-count: 1'> rec_type type somlreci1-rec_type,
mso-bidi- style='mso-tab-count:2'> end of ts_reclist.
mso-bidi- <![if !supportEmptyParas]> <![endif]>
but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
class="MsoNormal"> types : tt_reclist type table of ts_reclist.
class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
 data: t_reclist type tt_reclist.
and creating the structure based upon the structure definiton:
<![if !supportEmptyParas]> <![endif]> data: s_reclist type ts_reclist.
as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
 s_reclist-receiver = '[email protected]'. "<-- change address
mso-bidi- <![if !supportEmptyParas]> <![endif]>
mso-bidi- s_reclist-rec_type = 'U'.
and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
 append s_reclist to t_reclist.
<![if !supportEmptyParas]> <![endif]>
the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1"> style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>
class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
 EXPORTING
style='mso-tab-count:2'> document_data = docdata
style='mso-tab-count:2'> DOCUMENT_TYPE = 'RAW'
style='mso-tab-count:2'> PUT_IN_OUTBOX = 'X'
style='mso-tab-count:2'> COMMIT_WORK = 'X' "used from rel.6.10
 TABLES
mso-bidi-font-size: style='mso-tab-count:2'> receivers = t_reclist
class="style1"> <![if !supportEmptyParas]> <![endif]>
<![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
<![if !supportEmptyParas]> when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.
Hope this helps, Do reward.

Difference Between Data type and message type

Hi,
    i have doubt on data type and message type.why we are mapping the message type why not data type?wht is the difference between data type and message type?

Hi Narayanana,
Data type defines the structure of your xml message.Message type is the wrapper of data type.You will be using your message type while mapping and not the data type.Its the abstraction concept used in oops
kanan thiyam
Posts: 28
Questions: 7
Registered: 1/8/07
Forum points: 24
   Re: What is deffernce b/w Data type and message type
Posted: Jun 13, 2007 8:05 AM    in response to: suresh k         Reply      E-mail this post
Hi Suresh,
Data Type defines the structure of the message and it will be wrapped under Message Type.
Hope the details below will clearify your doubts.
A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
The characteristic of columns and variables that defines what types of data values they can store.
Check out the details:
http://en.wikipedia.org/wiki/Data_type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
Details:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
kanan

Diff b/w reference type and elementary type

hi all
can any one what is the diff b/w reference type and elementary type in data element ....
thanks
lokesh

The data type attributes of a data element can be defined by:
Specifying a domain whose attributes are copied by the data element.
Specifying a build-in type where the data type, number of places, and possibly decimal places can be directly specified.
Specifying a reference type, i.e. reference to a class, an interface, a type defined in the Dictionary, a built-in type, or a generic reference to ANY or DATA.
In the maintenance screen you can set the option you require by setting the appropriate flag (domain, built-in type, reference type) and filling in the corresponding input fields.
A reference type is a reference to another type. There are the following kinds of reference types:
Reference to a class or an interface
Reference to a type defined in the Dictionary
Generic reference to ANY, OBJECT, or DATA
Reference to a built-in Dictionary type with specification of the length and possibly also the decimal places
You can use a reference type to define the data type properties for a data element, or for typing the component of a structure or the line type of a table type.
In the field Referenced type, enter the name of a class, an interface, the generic references DATA, OBJECT, ANY, or the name of a type defined in the Dictionary. If the reference type is to be a predefined Dictionary type, choose the reference to the predefined type. Enter the number of characters and, if required, the number of decimal places.
where as
The data class describes the data format at the user interface.
If a table field or structure field or a data element is used in an ABAP program, the data class is converted to a format used by the ABAP processor. When a table is created in the database, the data class of a table field is converted to a corresponding data format of the database system used.
You can find a detailed description of the data classes allowed in the ABAP Dictionary in Overview of the Data Classes.

Automatic determination of Delivery type and Billing type in a sales order

Hi,
I want to know that in a sales order cycle, how does automatic assignment of delivery type and billing type takes place after we create a sales order?
For example,when I create an outbound delivery for a sales order of type normal (OR) then in that case how does the system knows that it has to create an outbound delivery of type LF.How does the system propses it automatically and same is the case of billing document.

Hi
In customising the sales document type (Tcode VOV8) -
specify the default Delivery type in the field DELIVERY TYPE in the 'Shipping' area of the sales document type customisation.
Similarly you can specify the billing type in the BILLING area for both Delivery related billing and Order related billing.
Thanks,
Ravi

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

How to trigger a form based on object type and process type

Hi all,
I am new into SRM.. I have been asked to develop a form by cloning an existing standard form..
Using bbp_output_change_sf badi you can trigger the form by passing the object type but the scenario is such that depending on the object type and process type the new form should be triggered.
The parameter iv_object_type passes the object type but how could i pass the process type ?
In the badi I noticed an import parameter is_event that has a field called transction_type that carries the process type but this field never got populated when i checked using debugger.
Please help as to how i can trigger the form based on the object_type and the process_type.
Thanx in advance.

Thanx again Jay Yang.. Well is there any possibility that you could get the items that were confirmed..
Let me eleborate..
Suppose in the PO u order an item for 10 nos and 5 gets confirmed and u return 2..
Well in my case it is that i need to fill up a field Qty returned / Qty confirmed..
I was able to get the number of items from the PO by passing the the passing the parameter to the FM "bbp_pd_conf_getdetaill"
but i dont know how to get the number of items been confirmed..
The quantity field in the line item structure gives me the number of items returned..
Can u tell me how to get the number of items been confirmed....

Calling Oracle Stored proc with record type and table Type

I have a oracle SP which takes record type and table Type which are used for order management.
Is there anay way to populate parameters with these datatypes and call the stored procedure using ODP.NET?
Please help.
Thanks in advance

Hi,
ODP supports associative arrays and REF Cursors. There is no support for PLSQL table of records.
Jenny

How does a record type and table type works

Hi,
How a record type and table type work for the ref cursor,
below i m giving an example but its giving me errors
can any one help me for this?
declare
type empcurtyp is ref cursor;
type rectype is record (veid t.emp_id%type, vename t.ename%type);
TYPE tabtype IS TABLE OF rectype;
empcv empcurtyp;
vtab tabtype;
begin
open empcv for select emp_id,ename from t;
loop
fetch empcv into vtab;
exit when empcv%notfound;
dbms_output.put_line(vtab.vename||vtab.veid);
end loop;
close empcv;
end;
here we hav table t and i m taking only two fields of the table t which r emp_id and ename.

Hi,
What errors are you getting with this? From experience you don't need a loop to put the records into the ref cursor its usually done on block.
HTHS
L :-)

Oracle Streams 'ORA-25215: user_data type and queue type do not match'

I am trying replication between two databases (10.2.0.3) using Oracle Streams.
I have followed the instructions at http://www.oracle.com/technology/oramag/oracle/04-nov/o64streams.html
The main steps are:
1. Set up ARCHIVELOG mode.
2. Set up the Streams administrator.
3. Set initialization parameters.
4. Create a database link.
5. Set up source and destination queues.
6. Set up supplemental logging at the source database.
7. Configure the capture process at the source database.
8. Configure the propagation process.
9. Create the destination table.
10. Grant object privileges.
11. Set the instantiation system change number (SCN).
12. Configure the apply process at the destination database.
13. Start the capture and apply processes.
For step 5, I have used the 'set_up_queue' in the 'dbms_strems_adm package'. This procedure creates a queue table and an associated queue.
The problem is that, in the propagation process, I get this error:
'ORA-25215: user_data type and queue type do not match'
I have checked it, and the queue table and its associated queue are created as shown:
sys.dbms_aqadm.create_queue_table (
queue_table => 'CAPTURE_SFQTAB'
, queue_payload_type => 'SYS.ANYDATA'
, sort_list => ''
, COMMENT => ''
, multiple_consumers => TRUE
, message_grouping => DBMS_AQADM.TRANSACTIONAL
, storage_clause => 'TABLESPACE STREAMSTS LOGGING'
, compatible => '8.1'
, primary_instance => '0'
, secondary_instance => '0');
sys.dbms_aqadm.create_queue(
queue_name => 'CAPTURE_SFQ'
, queue_table => 'CAPTURE_SFQTAB'
, queue_type => sys.dbms_aqadm.NORMAL_QUEUE
, max_retries => '5'
, retry_delay => '0'
, retention_time => '0'
, COMMENT => '');
The capture process is 'capturing changes' but it seems that these changes cannot be enqueued into the capture queue because the data type is not correct.
As far as I know, 'sys.anydata' payload type and 'normal_queue' type are the right parameters to get a successful configuration.
I would be really grateful for any idea!

Hi
You need to run a VERIFY to make sure that the queues are compatible. At least on my 10.2.0.3/4 I need to do it.
DECLARE
rc BINARY_INTEGER;
BEGIN
DBMS_AQADM.VERIFY_QUEUE_TYPES(
src_queue_name => 'np_out_onlinex',
dest_queue_name => 'np_out_onlinex',
rc => rc, , destination => 'scnp.pfa.dk',
transformation => 'TransformDim2JMS_001x');
DBMS_OUTPUT.PUT_LINE('Compatible: '||rc);
If you dont have transformations and/or a remote destination - then delete those params.
Check the table: SYS.AQ$_MESSAGE_TYPES there you can see what are verified or not
regards
Mette

Value Type and Report Type in Report Painter Report

Similar Messages

Maybe you are looking for