EC sales: tcode s_alr_87012400

Hi all,
When we are trying to generate report for EC sales for the quarter 4 2007, the system displaying details for only one output tax code 0%.
What could be the reason..! Regards SK

Hi Surya Kanth,
I have a similar problem but for Vendor masters. I want to default the reporting country and VAT registration number in FB60 and MIRO. Could you please let me know the note number that you applied?
Thanks,
Uma Toraskar

Similar Messages

SALE tcode is unuthorised in xi

hi all,
whe iam tring to create a Logical system in XI , the tcode SALE is bloced. when i am tring it shows"you r unauthorised SALE tcode".. how can i activate this t code.
is there another way to create LS for xi.
reply pls.
vijay

Try BD54

EC Sales Report S_ALR_87012400

HI Experts,
I need to run the EC sales list Report S_ALR_87012400 for our goods and services monthly and quaterly and after running the report I got the total vales in right hand side of the report but I dont want to get the total value here instead I need to split the amount for goods and service wise for our audit reporting.
Please any one expert in this help me out to sort out this issue ASAP.
Thanks in Advance,

Hello Shams,
Thanks for input , when I am entering reporting period I am getting below message -
and field is getting blank. What should be the parameters to run this report ? Any expert guidance on this.
Regards,
Sharvari Joshi

Changing GL Code for "Clring Account Revenue from Asst Sale" (TCode: AO90)

Dear Experts,
We have a requirement to change "Clearing Account Revenue from Asset Sale" from currently used GL Account (Eg; 22840020) with another GL account (Eg; 22840022). Both these GL Accounts are Balance Sheet Accounts. We have created required GL Account in desired conpany codes.
When we try to change respective GL Account in T-Code: AO90 (Balance Sheet Accounts) we get below message with green colour message type:
"Account "22840022" not allowed to be Balance sheet account"
"Account "22840019" not defined as P22840019L account"
(There are no red colour message type)
Please help. Should we go ahead with the change? Will there be any risk involved in doing so? Is there any other prereqisite to be followed?
- Nilesh

Dear Atif,
Thanks A lot for explanation.
Though fundamentaly it is right what you are saying, Our Client is using Balance Sheet Account 22840020 since many years as "Revenue from Asset Sale Clearing Account". Now they want to replace this GL Code with 22840022 (Balance Sheet Account). With previous GL Code there were no problems. And message given by system is relevant to what you are saying, but it is not an error message.
What I understand is, they are sufficing their requirement with Balance sheet account. So after replacing GL Code with B/S account there should not be any problem.
They do the retirement without customer and sale is not on credit basis also.
Please suggest for more clarity.
Thanks in Advance.
- Nilesh

2LIS_11_VAHDR not extract the latest sales

Hi gurus.
I need to make one query with the sales dates. For this, I use 2LIS_11_VAHDR and 2LIS_11_VAITM data sources. The problem is that the sources extract the date between 2003-2005. I need also the sales dates between 2005-2009. I don't haw to make to extract all dates. (when I run the extraction process I give the complete act.)
tank you

Hi
1) Deleting setup table : tcode :LBWG then give application component 11 (SD SALES BW)
But this would result in deletion of the data in setup table for all the data sources of 11 component.
2)Filling up the setup table for SD SALES Tcode : OLI7BW
Specify the data selection criteria, here u can give the sales documents ranges for ur required period
then
Give the Name the Run and give a future termination date for job Run and execute in the Background
3) Monitor the job then check the data in RSA3.
Hope this help..
Sonal...

Plants abroad: Customizing for stock transfer between plants, EC Sales list

Hello,
Please advice how the customizing for tax codes (output and input tax) should be done in order to get the SJ documents (stock transfer proformas) listed correctly in EC Sales list. Now the SJ documents are listed correctly in VAT report (S_ALR_87012357) but are not listed at all in EC Sales list (S_ALR_87012400) - and the correct situation is when they are listed in both reports (the amounts should correspond with each other). The main question is how to set up correctly the EU code (values 1, 3 or 9) in the tax code settings for three tax codes below:
1. output tax of departure country
2. output tax of recipient country (destination ctry) and
3. input tax of recipient country
Pls note that 2 and 3 together form the acquisition tax of the destination country.
Above three tax codes are now listed in VAT report but not listed in EC Sales list for departure country at all. SJ document should be listed in EC Sales list using the reporting country = departure country.
Any valuable advices warmly welcomed,
Kind regards,
Slawek

Dear Kumar
Please check the links
[Plants Abroad|http://help.sap.com/saphelp_46c/helpdata/en/e5/077f984acd11d182b90000e829fbfe/frameset.htm]
[Plants abroad: Sales-specific settings |http://help.sap.com/saphelp_46c/helpdata/en/34/60b19dae724effe10000009b38f91f/frameset.htm]
thanks
G. Lakshmipathi

Difference Between SCC4,BD54,SALE

Hi,
Can anybody help me on Difference Between SCC4,BD54,SALE
Cheers,
Nissu

SALE - Transaction code used for Interfacing with any application or business, Using which you perform some system settings for communicating and also performs monitoring.
SCC4 - Is a client registration, it is one of the Transaction code used for system settings and can found in SALE tcode.
BD54 - Is a Logical systems creation for system settings for communicating, also can be found in SALE tcode.
So, there is no need of having an idea to differentiate all.
Regards
Pothana

Idoc not received in xi

Hi,
i using idoc to file scenario . idoc are getting posted from sap sucefully i.e status 03 & no entries are found in sm58 .
I am unable to trace the idoc in xi i.e idx5 , sxmb_moni .
I have create port in idx1 for r3 also.
I am unable trace message in RWB .
Plz help me to solve this thread
Thanks,
Sridhar

Hi,
This are the ALE settings,
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

E-Recruiting : How to setup ALE for standalone setup

Dear experts,
We are implementing eRecruiting with the following setup:
ECC 603 on a separate server from eRecruiting 603.
I know that in such a scenario we have to transfer the data to & from ECC using ALE and IDOCs.
We have setup RFC connections between both the systems & defined the same in the table T77S0 (both ECC & eRec using HRRCF & DTCBA)
After this can anyone please specify what needs to be done?
I am looking for some kind of detailed information or a reference to any documentation will also do.What are the activities that BASIS needs to take care. Some of the things i am looking for answers are :
What are the BADIs that i need to activate both at ECC & eRec level?
How do i set up or build an ALE model?
How do i decide on the meesage type?
When should i use transactions PFAL & SALE & how do i use it?
How do i check that the data is transferred successfully?
Your inputs on these topics will be appreciated.
Thanks & Regards,
Sowmya

actiivate following badis and enhancespot implementations on e rec server
HRRCF00_SEARCH_RANKING
HRRCF00_DELETE_SPREL
HR_INB_PROCESS_IDOC
these are important for ALE point of view.
Steps for ALE
Go to the Sender HCM system Transaction SALE
Define logical system under basic settings
assign logical system to the client
Create an RFC connection to Erec server with the same name as the logical system name
add the user id and password (use system user with SAP_ALL)
Go to Communication under sale tcode
Determine RFC connection for method calls
Create Standard BAPI and DIALOG destination for the Logical destination
In SALE under modelling and implementing business processes
Maintain distribution models and views
Create Model View
Add a message type HRMD_A for the model view and add the sender and receiver system
Then go back to sale
and in partner profiles generate partner profiles put the model view sender system and user(system user)
go back to sale
goto Maintain distribution models and views
there select your modelview (just hightlight) go to edit->modelview->distribute
in your sender system in T77s0 table for RECFA DTCBA maintain the RFC name of the E-rec system.
Now login to Erec system
There maintain the RFC connection to E-rec system with system user
Goto T77s0 for RECFA HRRFC maintain the RFC name to HCM system.
Go to PFAL transaction in HCM sender system and for the model view/message type you have created send the data to e-rec
Regards,
Divya

IDOC to file scenario

Hi Experts,
In IDOC to file scenario i did in this way.
1)created logical system.
2)Using SALE tcode I assign logical system to client ,created RFC destination,Port and Partner's profile.
It is showing all the thing correct.
3) In XI system , I configured using IDX1 and IDX2.
Then I created the material and checked the status which is green in we05.
But in tcode IDX5, the material is not coming.
Here I am confused that why data is not coming to XI system.
can anyone help me?
Thanks
Rabi

Hi,
The Following are the Possible checks
1) Check in R/3 side SMQ1 & SMQ2
2) Check in R/3 side SM58
   In R/3 system, Goto SM58 tcode and see if the IDOC have stuck up in Queue.
   If the entry is available then select it and press F6, to push it manually.
    This happens normally if IDOC stuck up in queues.
3) Check in PI SMQ2 and IDX5
regards,
ganesh.

Branch VAT number in BSEG

Hi All,
The client is running EC sales report(S_ALR_87012400). And that report does not give the Branch customer VAT number updated documents(Credit memos) list .As BSEG table updates only main customer(Head Offfice customer )VAT number.
The issue is the report does not pick up the VAT number from Branch customer master where the main customer(Head Office customer) master is blank in VAT number filed.
The report picks up only when BSEG is updated with VAT number,and in this case the BSEG takes the VAT number from main customer master(KNA1) but not the branch customer master.
We found if any user exit exsists so as to include the code,but no user exit as such for this report.
Now the user wants all such documents (credit memosDG Document Type) to be listed with the branch VAT number in the report.
Please kindly help me if anyone has a way out for this issue.
early repsonse is highly appreciated and points will be assigned accordingly.
Thanks
Blessy.

Hi All,
I'm facing the same problem, kindly let me know how do I get the Vendor's VAT registration number while posting invoice. As every time when I'm trying to post vendor invoice the system ask for the customer number and the Reporting country and pick up the VAT reg. no. from the customer master base and not from the vendor master base.

Unable to convert the sender service insertgoods to an ALE logical system

Hi ,
I am trying to send an IDOC to sap system through XI BPM . But I am getting error as "Unable to convert the sender service insertgoods to an ALE logical system"
To rectify this error, I selected the integration process in integration directory and in (services---adapter specific properties I gave the logical system name as "LS" . Now i do not get any error in XI but idoc failed in SAP with error as "Partner profile not available "
Please advice .
Thanks & Regards,
Suvarna

Hi Suvarna
I have done this type scenarios using A2A and BPM also. I got success.
Here what i mean to say , forget about your integration process for a while.
For example you are sending a vendor file from System1 to a SAP System (IDOC). Here that file send by sender should be converted into IDOC.
So during the configuration of SLD for Sender system ,we should give logical system (any name) for Business System.
That logical system should be created in SAP system in (SALE tcode).Then you can't get that <b>"Unable to convert the sender service"</b>error.
For integration process no need to assign any logical system , leave it blank.
If you have any doubt you please call me on my mobile or give me your mail id I will forward the document which i have done.
thanks
Prasad 9960226467

ALE settings in sapR3 system logical system

Hi People
IN IDoc to File scenario
How to create Logical system(ALE settings) in SAP R3 system, i know little bit idea about that, we have to 1st create LS name (for R3 sys & PI sys), after that we have to assign that name's how to assign that, PLS can u provide me to with screen shots (if possible) r any links
Regards
shekar

Hi,
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

IDoc to XI u0096 Outbound IDoc

hi Experts,
Please let me know how to post IDOC to XI in R/3 Sender System?
Please help
Sourabh

Hi,
WE19 is the testing tool for the INBOUND and OUTBOUND Idocs,it will not post the data into XI.
What type of idoc ur using,To post the data into XI u have to trigger the IDOC in the transaction.
Suppoce u have to post the production order details then u have to go to CO02 TC code there u have to give the production order details and release the IDOC .
Before release the IDOC make sure u have done the ALE settings then the Data will be posted into XI.
Chech the ALE settings.
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

Regarding logical system function module....

hi all,
i migrated one interface program from 4.7 to ecc...both are seperate servers.....its working fine in 4.7 system...when it came to ECC.there s no errors...but in testing they found tat some system id is missing like tat...in RFC they called one FM OWN_LOGICAL_SYSTEM_GET........please guided me in this....

Ok sai. This interface is working in 4.7 why because it has the logical system name has been created and assigned to the client there. So, what you will do is take the logical system name given in 4.7. You can do that by going in to SALE tcode...under Basic Settings>Logical Systems>Assign Logical Systems
Here select the client name, and click on the button next to "change/display", that is the Details button. Here you can see the logical system name. Note that.
Now, in ECC 6.0, go into SALE tcode and then follow the same path...But instead of assign logical systems,select define logical systems. Now, click on New Entries button and then give the name you have in 4.7 and then give the same name in 6.0...and give a description. Save it..
Come Back,, now click on assign logical systems and then move into change mode....then select the client u logged in with and then click on details tab and here change the logical system name. Give the logical system name you just defined. Save it...and come out.
Now, try executing the Interface you migrated. And revert back with the error if there is any.
Vishwa.

EC sales: tcode s_alr_87012400

Similar Messages

Maybe you are looking for