Transaction and SPRO transaction codes in SNC

Hi,
Can anybody provide the transaction codes used in SNC and also SPRO transaction codes.
Thanks

Dear Vaibhav,
Some transactions:
/SAPAPO/MAT1, /SAPAPO/PRT_LOCPROD, /SAPAPO/LOC3, /SAPAPO/TL1, /SAPAPO/MTI2, /SAPAPO/RELHSHOW, /SAPAPO/RELHDELETE, /SCA/KANBANMDV, /SCA/SUPAREAV, /SCA/UPDRESPTIME, /SCA/SCHEDCFG, /SCA/SNIALERTSWRITE, /SCMB/48000030, /SCMB/15000010, /SCA/BIF_EVSTA_C, /SCA/52000046, /SCA/52000012, /SCA/SNIALERTSWRITE, /SCMB/ALEN_ALERT_DEL, /SCA/94000326, /SAPAPO/REPLCTRL, /SCA/FCSTMR, /SAPAPO/PROM_EVENT, /SAPAPO/SCMB_MP32, /SAPAPO/MP_CBPF, /SAPAPO/PROM_PATT, /SAPAPO/PROM_OFFSET, /SAPAPO/PROM_PROF, /SAPAPO/PROMMR, /SCA/94000263, /SCA/DELCLOSEDKNBN, /SCA/09000444, /SCA/60000197, /SCA/60000198, /SCA/FCST_OUT, /SCA/DMD_INF_OUT,
You can see the transaction codes by clicking on the icon at bottom right corner of the SAP screen. You can note down and maintain a list of codes you use.
Search the forum or internet for general transaction codes for SNC APO.
Regards
Naveen

Similar Messages

What is difference between enjoy transactions and Normal transactions

What is difference between enjoy transactions and Normal transactions
Ex:- ME22 & ME22N
What is difference between these two.

hi ,
the transaction code with 'N' are created with help of object concept.
In your case ME22 is obsolete one and ME22N is the tcode created with object concept.
pls Reward helpful points
Thanks
Siva

When to use Global transaction and Local Transaction only

Hi All,
Could you please help with this question thats been troubling me from quite long time.
When to create Global & local Transactions and Local Transaction Only while creating Data source on oracle Application Server 10 G.
Do I get any advantages by using Global & local Transactions for creating Data Source
Thanks In Advance.
Regards,
Ajay Kumar .Akula

mattyG wrote:
What is the difference between a single-process shared variable and a local variable?
A single process shared variable is more like a global variable, because it can be accessed from any VI in your hierarchy. Local variables are strictly local to the single VI where they reside.
Shared variables are a relatively new feature, while local and global variables are ancient. As such, shared variables are in many ways more modern and integrate better into state-of-the-art coding guidelines.
Shared variables contain error terminals so you can enforce execution order. local variables have no such thing.
A shared variable can stand on its own, while a local variable is always tied to a front panel object.
You need a project for shared varaibles.
You can easily turn a single process shared variable into a network shared variable later in the development, without the need to rewrite any code.
LabVIEW Champion . Do more with less code and in less time .

Material Transaction and Move Transaction Managers are Going Inactive

hi
it was running previously but currently it becomes inactive.can any one tell in which table to look for the error related to this problem?
Kind Regards
Sayantan

Hi;
What is your OS and EBS?
It was working before? If yes what have you been changed on your system(patch etc)
Please check below note:
Material Transaction And Move Transaction Managers Are Going Inactive [ID 93507.1]
Material Transaction and Move Transaction Managers are Going Inactive [ID 98757.1]
Regard
Helios

Problem with use of COM+ Transaction and DB Transaction

Problem with use of COM+ Transaction and DB Transaction
We build a Web site that use sometime COM+ Transaction and sometime DB
Transaction. If we use a COM+ Transaction and a few seconds later we try to use
a Database Transaction (OracleConnection.BeginTransaction), we get the error
Connection is already part of a local or a distributed transaction
Of course the error does not produce everytime; it takes some try before we get
the problem. And of course, if i use pooling=false on the connection string,
the problem does not appear.
i run the Web page
and push the COM+ Transaction and DB Transaction one after the other for some
times and the problem should appear.
Environment: Windows server 2003, .Net Framework 1.1, ODP.Net 9.2.0.401,
Database Server 9.2.0.4

> Why in form builder can't I...
Is this happening at runtime or at buildtime? You'll need to provide more info on what you are actually doing that's causing the problem.
Regards,
Robin Zimmermann
Forms Product Management

Different Exchange Rate between Daily Transactions and Tax Transactions

Hi All,
I would like to ask abount define Exchange Rate for tax calculation. I set our standard exchange rates (For Daily Transactions) by using exchange rate type 'M'. But I want to calculate the tax element using exchange rate type 'T'. It is because there is a different exchange rate which is used for Daily Transaction and Tax Transactions. Does anyone know a way of doing this in config to separate this exchange rate for tax calculation?
Thanks for any help,
John

I think its a bit misleading...The requirement is to post an Invoice with a base taxable amount of Exchange Rate A and a tax amount of Exchange Rate B. The Base Currency is JPY and the System Currency is SGD. So the Report S_ALR_87012357 should see the amount in SGD there. The Issue is caused by the different exchange rate on the tax amount submitted by the Vendor Invoice.
Example: Vendor Invoice Amount: 926,413.00 JPY, then we created PO to Invoice with Base Currency JPYalso amounted 926,413.00 JPY. However, in the Vendor Invoice Amount, the Tax Chargeable is 923.00 SGD (based on their exchange rate 65.66 JPY per SGD). But our Exchange Rate (System Rate) is 63.49 JPY per SGD. How can we reflect the Tax Amount as 65.66 JPY but still the correct SGD amount is based on the Vendor Original Invoice Exchange Rate 65.66 and not the System Exchange Rate, 63.49 in the same Invoice Creation (MIRO)?

Transaction support? Can i coordinate EJB transactions and COM+ transactions?

Can I call a transactional com object within an ejb transaction and have
success/rollback handled correctly? Or will I have to hand-code this? Are
any examples available?
Niels Harremoës
PricewaterhouseCoopers

WebLogic jCOM does not support coordination of transactions over COM+. There
are no examples of manual transaction coordination in the WebLogic jCOM
examples, and at present BEA has no plans to create one.
Chris Hopper
BEA Systems, Inc.
"Niels Ull Harremoës" <[email protected]> wrote in news:3bcc91f4
@newsgroups.bea.com:
Can I call a transactional com object within an ejb transaction and have
success/rollback handled correctly? Or will I have to hand-code this? Are
any examples available?
Niels Harremoës
PricewaterhouseCoopers

Different Baseline Date in Invoice Transaction and Payment Transaction

Hi All,
I have one issue. When I post the invoice transaction in FB60 and input the baseline date 22.08.2011. Then I post the outgoing payment with document date 20.08.2011 and then I checked the baseline date in vendor line item, the baseline date not in 22.08.2011 but it is defaulted into 20.08.2011 (document date when perform outgoing payment). Why the system cannot link the baseline date in invoice transaction and document payment? It makes unconsistency in baseline date. Kindly need your help to share if you ever found the same issue like this and also the SAP Notes if you have it.
Thanks a lot.
Best Regards,
John

Dear John11
If your selecting your payment terms in invoice system automaticaaly pics dates what you config. in OBB8
But it is not requried to give any baseline date for payment transaction
Regards
shankar

Source transactions and destination transactions

hi,
In HFM9.3.1, we have created some consolidation rules but we are unable to get transaction details while
performing the following action on the data grid.
select account -> right click-> destination/source transactions
The list always appears to be empty, irrespective of whatever complex consolidation rule we write??
Are there any specific settings required to enable this feature.
Pls, help me out.

The transaction details report, always considers your point of view, therefore, you will get different information depending on whether it is a parent account or a base level. If it is a base level account the support will only apply to the custom dimensions. If it is a parent account, you won't see line item detail or J/E or audit detail. Also, you may want to check your display options for journal details, and Custom dimension supression, and all other options.

Technical difference between SAP enjoy transaction and Old transaction

Can some one detail out technical differences betwwen SAP enjoy transaction ( like ME21N) and normal old transaction( like ME21). Specially I want to know the difference between user exits for two transaction .

First the user exits will be the same, the reason is that you must get the same result whether you use the ME21 or the ME21N. The difference is the UI, or user interface, the enjoy transaction leverages the new control framework which was introduced in 4.6. These controls include tree controls, alv grid controls, docking controls, picture controls, etc. All which can be found in the ME21N. The ME21 transaction uses the classic dynpro technology without using the control framework.
Regards,
Rich Heilman

Create transaction and screen variants

Hello
I want to create transaction variant for VA01 and MM01 in order to simplify the data entry. I know SAP has SHD0 as a tool and Synactive has GuiXT to make all these changes. But I wonder what are the differences between these 2 tools.
Please let me know,
Thanks,
George

Dear Mr.George,
Transaction Variant
You can only create transaction variants for dialog transactions and reporting
transactions.Only "normal" screens, dialog boxes, and subscreens can be
included in the variant.
Screen Variants are automatically created anytime you create a
transaction variant.
Initial Screen
Enter the name of the transaction and the transaction variant on the initial screen. The system creates a cross-client transaction variant. If you want to create a client-specific transaction variant, choose Goto -> Client-specific transaction variants tp branch to the client-specific transaction variant maintenance transaction.
Client-specific transaction variants only exist in the client in which they are created. The field contents of the transaction variant must be available in this client. Cross-client transaction variants are available throughout the system, regardless of the client currently being used. The field contents of these transaction variants must be available in all clients.
Creating the Transaction Variant
Choose Create to create a variant.
The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).
Here you can determine:
if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)
if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")
if field contents are saved (the "With contents" checkbox)
if the ready for input status of specific fields should be revoked (the "Output only" checkbox)
if specific fields should be hidden (the "Invisible" checkbox)
if specific fields should be mandatory the "Mandatory" checkbox)
You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).
Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).
Choose the function Continue to proceed. The following pushbuttons are available:
The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.
The Menu functions function displays an additional dialog box wher you can deactivate menu functions.
The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).
The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
Enter a short text for your transaction variant here.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
You can also branch to this list using the Change values function during the function selection process.
Deleting Preassigned Values
You can delete all of the values you assigned to fields of a single screen in a transaction variant by resetting (deselecting) the Adopt field values checkbox. This deletes the screen from your variant, even those entries that were transferred to the variant during previous processing.
If a screen variant has already been created for this screen, then the system simply deletes the screen variant's transaction variant assignment; the screen variant itself is not actually deleted.
Individual fields can be deleted from transaction and screen variants by resetting (deselecting) their corresponding checkboxes.
If useful reward points.
Regards
Mangal

Managed datasources, Global transactions and XA

I have a question regarding the use of managed datasources and global transactions with oc4j 10.1.3.
From the documentation at:
http://download-west.oracle.com/docs/cd/B25221_04/web.1013/b14428/servdats.htm#CHDGJECC
I conclude that managed datasources by default support global transactions.
I have tested the following scenario:
A stateless session bean starts a container managed transaction. The bean updates data in two different databases through two different
managed datasources. The transaction is atomic.
What surprises me is that this works. I would think that I would need to configure the datasources to make use of XA.
Can someone explain why this works, wat is the difference between XA transactions and global transactions in this context?

Further to give more info the error users are facing is
Could not connect to 'oracle.jdbc.xa.client.OracleXADataSource'.

SPRO Transaction code

Hello
In many of the IMG SPRO transaction we could not see the transaction code. Only spro is writeen infront of transaction.
How to find the Transaction Code of such transactions.
Please Guide
Regards
Sachin

Dear Sachin,
After going to Display IMG screen->Additonal Information->Additional Information -
>Display Key--->IMG activity.
After executing this,against each node,you will get the img activity under additional information and take the last 4 characters
and this will be the T Code for executing directly.
Say for Eg:for BOM Item categories, it will display SIMG_CFMENUOLPSOS13,so take this OS13 alone.
Or else you can check using SDMO.
Regards
Mangalraj.S

Difference in Account Code combination at Transaction and Accounting entry

Hi All,
We are working on Subledger Modifications (SLA) for a Client in order to meet few key business scenarios... Even though we were able to achieve the desired outcome through SLA, client is not pleased about the fact, there exists two different account code combinations for a transaction i.e.
1) The account code combination that is defaulted or entered in the transaction
2) The account code combination that is used for creating the accounting entry considering the modifications done at SLA.
There is a difference between the above two, due to modifications carried out in SLA.
Since the scope of SLA is limited only to make changes at the Accounting entry level, such variations would exist, however client is not comfortable with such an approach.
We are performing the SLA changes for three modules: 1) Cost Management 2) Accounts Receivables and 3) Accounts Payables
If someone has worked on such similar situation in your previous assignments, perhaps you can share how the same was addressed.
(Such as any customizations, Workarounds, irrefutable justifications etc ..)
Thanks and Regards,
Karthikeyan

Hi,
Check is there any restrictions are there . the data must be displayes if the data is there in infocube.
Regards
sivaraju

Dangerous APO and BI Transaction codes

Hi experts,
I have question Dangerous APO and Transaction codes
Background :
We are in the process of implementing SOX controls for the new APO and BI Systems
Questions :
What are the Dangerous APO Transaction codes which should not be assigned to any one in Production system
What are the Dangerous BI Transaction codes which should not be assigned to any one in Production system
Additional Notes
System which we are having
APO
Version : SCM 5.0
BI
Version : BI 7.0

Praveen,
I am a puzzled that you would ask such a question.
Authorizations ALWAYS derive from requirements. In this case, Sarbanes-Oxley speaks of control mechanisms. Your SOX auditors should tell you what they consider to be critical, and they should advise the client company as to which transactions should be controlled, and how best to control them.
There is no transaction that should be disallowed to everyone. That would eventually make the system unusable. The question is, "how many people should have these critical transactions, and how should the execution of these transactions be monitored and controlled".
Generally, the APO portion of SCM should require less SOX controls than ERP, since APO is mostly a planning system, and not an execution system (there are some exceptions here though). Likewise, the BI portion of SCM usually contains no financial reports, and therefore should have relaxed controls over, say, the main BI instance used by your company.
Don't make the mistake of strangling yourself to satisfy your perception of what you think an auditor may require. Make them tell you the minimum requirements for compliance. Anything beyond minimum compliance with SOX is costly. This question is then a matter of your company's policies. I usually vote for 'no additional restrictions' (but my poor vote doesn't usually count for much).
Rgds,
DB49

Transaction and SPRO transaction codes in SNC

Similar Messages

Maybe you are looking for