ABAP query related to IDocs

Hi All,
My ABAPers had done settings for IDocs a month back. We were able to post finance documents. Now we are getting following error:
"No cross-system company code is defined for company code ..........
Message no. F1302
Diagnosis
ALE distribution scenarios in your system are active with at least one of the FI message types FIDCMT, FIDCC1 or FIDCC2 for the distribution of FI data.
The ALE distribution can be activated for all or for individual company codes - the activation is done using the cross-system company code.
The system uses the cross-system company code to check whether ALE is active for this company code.
As well as their local company code ID (example: 0001), these company codes also have to have a cross-system company code ID (example:EUROPA), irrespective of whether a company code is to be dispatched.
System Response
The data is not posted.
Procedure
Carry out the following activities in ALE Customizing under 'Global Organizational Units':
1. Cross-System Company Codes
Proceed
2. Assign cross-system company code -> Chart of accounts
Proceed
3. Assign company code -> cross-system company code
Proceed"
When we completed the above 3 steps, by assigning same company code to the company code on which we are working, the documents are posted but are cleared simultaneously.
Please guide us how to overcome this problem. Your advise will be a great help.
Thanks in advance from our team,
Amish Shah.

There is no reply to this question. However, the error got solved by changing the customization in IMG, ABAP workbench. Here, we assigned the Company Code to the Global Company code.
Thanks everybody......

Similar Messages

Regarding ABAP Query related

Hi,
Can any body tell me how to keep query related data in
internal table?
Regards,
Suresh Kumar.

Do you mean that you are running a SQ01 query and you want to get the data from it into your report program?
If this is the case, the normal way that we pass internal tables and stuff from program to program, is thru IMPORT/EXPORT statements. But since you are talking about a query this may be a problem in adding the EXPORT statement to it.
Regards,
RIch Heilman

Query related to idoc

Hello Friends,
I am not able to understand the meaning of this:
Please can anybody help me to understand this ..
IF gv_po_type = 'YI1'.
Scan though the entire idoc (internal table IDOC_DATA) and build an internal table T_EKPO that contains the fields;
purchase order number like EKPO-EBELN from E1EDP02-BELNR where QUALF = 001
purchase order item like EKPO-EBELP - from E1EDP02-ZEILE where QUALF = 001
purchase order item qty like EKPO-MENGE from E1EDP01-MENGE
confirmed qty like EKES-MENGE - the total of the E1EDP20-WMENG segments for the item
Regards,
Shreekant

Hi Shreekant,
It means that if the purchse order is of type YI1 , then get the idoc data into internal table with the specified criteria.
Regards,
Chandan

ABAP query to be modified

Hi,
I have one ABAP query which is already created by someone. I want to ADD one field in where condition.. How do I do itu2026Need to add it in where condition in select query.
I want to know the steps to be followed..
Thanks
RB

HI Ramesh,
Here are some information before you modify ABAP query relating to other developer.
To use an ABAP query, the user must have appropriate authorizations. Two ways of providing authorizations to the users are as follows:
- User groups
The user should be a part of at least one user group to run the corresponding ABAP query. This automatically restricts the access of the user to specific functional areas, and thus the corresponding underlying logical databases.
- Authorizations
The authorization object S_QUERY should be used to give proper authorizations to the user for a query. This authorization object has a field named ACTVT which can take values 02 for Change, 23 for Maintain and 67 for Translate.
This value determines whether the user can create and modify the query. The possible authorizations in the object are as follows:
S_QUERY_ALL Change, maintain and translate query
S_QUERY_UPD Change and Translate
Hope this information can help you.
Best Regards,
Krishna

Hi friends, IDOC and RFC are sap related.but idoc is in abap stack rfc is

1)IDOC and RFC are sap related.but idoc is in abap stack rfc is in java stack.what is difference between two.?

hi ganga,
The IDoc adapter is used by SAP systems to connect to a centrally configured Integration Engine using IDocs
which is properitory to SAP integration
so it doesn't need the Adapter engine.
refer:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
The Adapter engine is working on the J2EE Engine.
RFC Adapter is provided by the AdapterEngine.
So RFC needs Java Runtime where IDoc doesn't.
refer:
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
regards,
nikhilbos

ABAP Query Transport request related

Hi,
I have created a Abap query,
1) User group
2)Infoset
3) Query
But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
Development
Please suggest, is this std behaviour or is anything missed
Rgds,
Jai

Thanks to all,
I just created TR with new package for user group and included ifoset and query in the same TR
and imported, issue is resolved
But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
Short text
SAP Query: Transport tool
Description
The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
General information
Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
In both cases, you have to perform similar actions.
The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
Transport action EXPO (exports)
If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
The import options, each of which has an abbreviated syntax,
are as follows:
REPLACE or R
MERGE    or M
GROUP=ug or G=ug    (ug = name of a user group)
UNASSIGN or U
If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
This transport type allows you to transport a modified InfoSet and all the associated queries.
For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
Transporting a user group
Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
Entering a new member in a user group in the target client is possible only if a user master record exists.
In the target client, the assignment of InfoSets to this user group remains.
Transporting an InfoSet
Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
Transporting a query
Transporting a query means only the query itself is transported.
Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
Transport action IMPO (imports)
If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
Transport action SHOW (display)
All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
Transport action DELE (delete)
All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
regards,
Jai

ABAP Query - Sorting Issue in Basic List (SQ03)

Hi,
I have developed a ABAP Query. I want to sort some of the fields, for which I need to add some output fields to the sort sequence box in the Basic List page in SQ03/SQ01. But, I am not able to drag and drop the fields directly. Please suggest how can this be done? Thanks in advance.
Best Regards,
Tejas Savla

Hi Abhishek,
There are three things related to Query.
1) You have to create the USER GROUP in SQ03.
2) You have to create the Infoset in SQ02. In this infoset you can write the logic of the program/Query what ever you want to perform.So you can sort the table in the infoset in the program logic.you have to create the output table of the query.
3) you have to create the Query in SQ01 and you have to associate the User group and infoset . you have to design the layput of the output you want to have.this output fields would be same as you have defined in infoset(step 2).
hope this will help you.
thanks
Tanmaya

Role of abaper's in ALE/IDoc's

Hell all
I am new for ALE/Idoc's . can anybody tell what is the role of abaper's in ALE/Idoc's.

Hi,
Message types (required for sending the data across participating systems)relate to the structure of the data called an IDOC (Intermediate Document).Message types provide the format of the data, which can be exchanged betweenSAP and non-SAP systems. ALE supports over 200 message types in R/3.
Also check the below links
http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
http://www.sap-img.com/basis/types-of-idocs-use-in-ale-configuration.htm
Thank U,
Jay....

ABAP Query - output entries repeating

Hi Friends,
I have created an ABAP query but the output entries are repeating. I tried different joins but dint work. I found out the internal table in the query report in SE38 and used the following command in the Infoset code (SQ02):
DELETE ADJACENT DUPLICATES FROM %G00.
I am not able to generate the infoset without declaring the internal table %G00. Hence I declared it in the DATA section of the infoset code. After this when I go to the query (SQ01) and run it, the system is throwing an ABAP dump which says %G00 has been declared twice.
Can someone plese help me out in getting this resolved. I've been stuck with this for almost a week now.
Thanks in advance,
Dikshitha

Hello Dikshitha,
In the data section of the infoset:
Deletion of duplicates lines
constants : wk_table(6) VALUE '%G00[]'.
FIELD-SYMBOLS : <t1> TYPE table.
In the END OF SELECTION (AFTER LIST):
the other code lines.
I checked my infoset, I never declare %G00[] as it is automatically generated. Perhaps you forgot to remove some of your previous code lines? Have you check everywhere (code related to additional fields, code tab, data read prog tab?).
After the modification, try to create a new query from scratch related to this infoset. Perhaps it's a "refresh" problem.
Olivier

Query related to filter group on matnr created in ALE distribution model

Hi All,
I have query related to filter group on matnr created in ALE distribution model.
I have created a filter group on matnr in ALE distribution model and put the value E* ( purpose is that all the material number started with E should be triggered in case of any changes in the material).But it is not working.
<b>Can anybody suggest the solution for this i.e how to capture E* value for the material master changes and should trigger idoc using change pointer using BD21.</b>
Thanks & Regards
Prabhat

Unfortunately, you cannot filter using wildcards or exclusions. You have to explicitly list each allowed value in its entirety.
In my opinion, the simplest solution would be to copy function MASTERIDOC_CREATE_SMD_MATMAS, modify it to handle your custom filtering and update the message type entry in transaction BD60.

Pricing reports,ABAP query based repors

hai
pls tel me the how to prepare the pricing reports as well as abap query based reports
thanks in advance

Dear sri vijay ,
Please read the rules of engagement before posting in forum
Please search the forum before posting
I am sure you will get lot of past threads related to ABAP Query and Pricing Reports.
Thanks & Regards,
Hegal K Charles

I am designing ABAP query in SQ01 i have not get one field MATNR

Dear All,
I am designing ABAP query in SQ01for MEK2 for Report.
I have not get one field MATNR
I have two table konp and konh i have design in SQ1 i am not get field regarding this table .
Please Help me.
Thanks in Advance.
Regards
Kumar

Dear Clemens
I want MATNR FIELD related to these table.
I am using KONP AND KONH TABLE .
Regards
Kumar

ABAP Query: How to transport?

We have created one ABAP query in Development system. In Query we did some changes related to code.
We want to transport it to Quality system.For this we are running "RSAQR3TR" program in Devp System . through which we are exporting "User Group, Infoset, Query" in same sequesnce, Which is generating request.
After transporting it to Quality, We are Importing it by running same program.
User group, Infoset , And Query Layout is getting updated but it is not updating the code which we have added into the query.
Please advice

Hi Reddy,
For the second part of question :
When you create a abap query SAP generates a program at the background. You can copy that program to a Zprogram and assingn a Tcode to it.( You can add some more features to the report like drilldown etc.. )
Your technical consultant should be able to help you out on this .
Regards
Balaji

Regarding ABAP Query authorization group

Hi Team,
This is regarding ABAP Query!
I have created one authorization group, for testing i have assigned my id in authorization group.
After creation of ABAP query,standard program got generated. Now i have created one transaction code at the last for the ABAP Query.
Now the isse is even though i have deleted my id from the authorization group. I am able to execute the query from SQ01 and with the Transaction code .
It should not happen...i want who soever id is mapped to the transaction code ...that member should only be able to run that query, otherwise there is no use of authorization group.
Please help me out in this case.
Thanks & Regards,
Anil Kumar Sahni

Are you sure that you don't have access to that authorisation group? Execute report RSUSR002. In the 'Authorization Object 1' block inform S_TABU_DIS in 'Auth.Object' and accept. Then inform Activity=03 and Auth.Gruop= your group.
You will get a list of all the users which, theoretically, will be able to execute the query. If you press 'Roles' or 'Profiles' in the toolbar of the listing you will get to know why you have authorisation. May be you have the SAP_ALL profile.
Also, one more thing to take into account: how have you created your transaction? Is it referring directly to the generated report? Then it is an error, you should execute program SAP_QUERY_CALL. Read this post: [Relate transaction to query;

Transport abap query from one client to another--v--urgent---v----urgent

hi,
i have an abap query in one client and want to copy to another client.can i do this if so what are the steps involved .i tried the options like in query go to environment and then to transport .i also tried to do by running the programe RSAQR3TR.but it was transporting in the same client .i want to transfer into another client.plz help me out asap .

hi,
Create a request related to that Table Definition and add data content in the request like
R3TR-TABL-<table name>
R3TR-TABU-<table name>
R3TR-TABD-<table name>
and release the request
Take the DATA files and CO files related to that request in a Pen drive and put the same into the new server DATA and CO files and import using STMS.
For new program, it gets transported along with the program.
For changed program (which has already been transported once), you need to include texts in transport request - just go to Selection texts, save them in the transport request and you're all set.
whenever you assign a request number to the program
and also the selection texts willbe stored under that request number
so when u release the program
the selection texts will also go
after releasing the request if you change only the seleciton texts
only the changes done to selection texts will reach the target
and the rest of the things remain same
so when ever you release a request all the things under that request
will go

ABAP query related to IDocs

Similar Messages

Maybe you are looking for