"code level" document comparison software

i have been using TextWrangler and am just about to purchase an Araxis Product in order to /compare/ two or three or more documents in the hopes that i can highlight the differences and even print them out like this.
i wanted to check in with the list in case anyone had any software suggestions for particularly visual tools that do this and also to confirm that TextWrangler is not really the tool for this.
TIA

hotwheels 22 wrote:
x, did i miss something in text wrangler or is it just showing me a text based /description/ of the differences below? am i missing a setting because i am not seeing a visual readout which i really need - and really would like to be able to print out as well.
No you aren't missing anything. It is a textual compare but it shows the two files to be compared side-by-side and when you select a difference in the bottom window it will highlight the differences in the two file windows above. I actually prefer this to the "cutesy" FileMerge because I prefer to do all my edits in a single app (BBEdit) as opposed to using yet another app.
If that isn't good enough and you don't want to install all of xcode with FileMerge there are plenty of alternatives. Stick "compare" into a macupdate.com search.

Similar Messages

Where we assign Exchange rate type at company code level,

Dear All,
Where we assign Exchange rate type at company code level, In 0BA7 we assign by Document type wise and OB22 will assign by controlling area wise , but we are not maintain Controlling area, exactly where we assign , and how it will pick at the time of PO creation ,
Thanks in advance
Vijay

Hi,
In OB22 we assign Exchange rate type against company code and not against controlling area .
Regards,
Shayam

Material valuation at company code level

Hi,
We have the valuation at company code level and when we transfer material from one plant to another (Two step stock transfer) the system dont post fi document. When the profit center of the material is assign an fi document is posted. Somebody knows why?
Thanks
Edited by: Elisabete Cuellar on Jul 27, 2010 11:56 AM

you have valuation at company code level.
both plants are in same company code, so same valuation level, so no FI document created , the FI docuement not required here
For profit center, FI document will be ceated for that profit center.
This is standard process only

SAP ISU- Can you help on Invoice Rounding steps at company code level,

Dear Friends,
Can you help on SAP ISU Invoice Rounding steps at company code level,
Client requirement is: - for one company code they need round the Invoice and other company codes they does not required the round option.
We have configured some steps, which are given below,
Contract Accounts Receivable and Payable - Basic Functions - Postings and Documents
1.     Define Rounding Rules for Currencies
2.     Define Accounts for Rounding Differences
3.     Accounts for Rounding Gross Amounts (IS-U)
4.     IS-U: Define Acct Assignment Data Relevant to Transactions
a.     (Main Transaction 0010 and Sub Transaction 0040)
SAP Utilities u2013 Invoicing
1.     Define Basic Settings for Invoicing
2.     Define Invoice Rounding Rules
Please provide the solution; I will be appreciating for earliest answer...
Thanks and Regards,
Prudhvi

Hello Christiane,
Thanks for your quick reply, and valuable information,
But we have u201CNo roundingu201D option available at client level, path has given below,
SPRO u2013 SAP Utilities Invoicing u2013 Basic setting u2013 Define Basic setting for invoicing
We are not authorized to change any configuration at client level,
If you can able to guide me at company code level that could be great,
Thanks for the support
Thanks and Regards,
Prudhvi

Payment block non editable on the basis of company code level

Dear Gurus,
we had made payment block "A" non editable in payment praposal through transaction code ob27.as per reqeust from
our partent company in India but our subsidiary in France wants the payment block "a" to be editable (to be insert
payment block "a" in document to make document deselect). Is it possible to make payment block editable on the basis of
company code level.
Regards,
Rajesh

Hi,
In this scenario, you need to have a NEW Payment block key like Z. Create Z with reference to A in OB27.
For Z, you need to select check box Change in Payment Proposal and SAVE.
Now maintain this Z in vendor masters of company code, where you want the payment block can be edited.
Note: Payment Block codes are not company code dependent.
Regards,
SRinu

Account Determination at Company code level for an interface

Hi All,
We need an account determination table at company code level that will be used by an interface to find the GL accounts for a particular company code.
This is required for interfacing certain GL documents onto SAP and the account determination need not be hardcoded in the program.
Kindly revert with your ideas.....
Regards,
Gangs.

Hi Gangesh,
All the account determinations will be done only at the Chart of Accounts level only. You cant show me even one account determination which will be done at the company code level. (without giving chart of accounts before assigning a GL)
So only table T030 will be the right table for you. Hope you understood,
Regards,
Sreekanth....

Restrict PO at company code level

Hi,
We have near about 10 number of company code and lot of plants attached to each company code.
and only one purchase organisation.
Now business require that PO shold be created only for 2 company codes not for all. there are alreday roles available for PO creation .
Now how to restrcit the PO creation at company code level because at plant level it is not possible due to large number of plants.
Regards,
Pardeep Malik

Hi,
Please kindly be informed that the following authorization objects are checked when an Enjoy purchase order is created (activity 01) or changed (activity 02):
- M_BEST_BSA (document type in PO)
- M_BEST_EKG (purchasing group in PO)
- M_BEST_EKO (purchasing organization in PO)
- M_BEST_WRK (plant in PO)
So this is somthing you can not solve by only using roles. You will need as suggested to make the check in the BADI.
Best Regards,
Arminda Jack.

Is it possible that we generate material requirement in MRP at company code level?

We want to generate material requirement in MRP at company code level, what is the possibility or any work around.
Thanx in Advance.

Hi Mirza
This is not possible on the standard system. The highest planning level on MRP is the plant.
It has been discussed on the following thread, where BAdI MD_CHANGE_MRP_DATA was proposed as a solution, however, the logic to be implemented on this BAdI is very complex:
MRP Run considering Stocks for Multiple Plants and Requirement maintained for Plant Cluster
If you want to know more about the BAdIs available on MRP check the following document:
BAdIs for MRP
Another alternative is to use flexible planning to plant at company code level, then disaggregate the planning to the plants and transfer the result to demand management and MRP.
See the following thread for details:
Flexible planning | SCN
BR
Caetano

MIRO number range tobe separated at company code level

Hi All,
Can anybody tell me how to separate MIRO number range at Company code level. We have 3 company codes in the same client. Cant we have different company codes for 3 of them. If yes, where to do the required

Hi
Refer the below post
Different No Range for invoice document no(MIRO) - company code wise.
Thanks !
E.Avudaiappan

Valuation Area at Company Code level

Hi,
In what ideal business case/industry one should set valuation area at company code level when SAP recommends valuation area must be set at Plant level ? in other words..what is the practical purpose of Valuation area at company Code level?

Hi
Think that valuation area link with records in table MBEW. So, if you have a company with 3 plants, and you have a single valuation for all company, in 3 plants the valuation of materials are the same, with their implications in valuation of stock and valuation of margin in sales (remember that this value can flow -really, use to flow- to condition VPRS in SD, well see SAP Note 1365939 - VPRS logic and Customizing settings in SD and SAP Note 547570 - FAQ: VPRS in pricing for more details). If you do a valuation different by plant, stock and margin calculations are different.
What are the elements that you must considerer?
1. If the materials is purchased, think if the same material have different conditions (different conditions in MM, for instance, indirect costs as shipment costs, different vendor with meaningful differences in prices or discounts). It's indiferent that it is a raw material or a material that you can sell. The raw material will work in product costing as an item in BOM. First of all, considerer the impact in stock value, second think how is delivered the materials to customer from plants and their impact in profitability analysis. If there are meaningful differences for the same material between different plants and you give the same value in all company, depending of the mix perhaps your customer is fooling himself about this issue.
2. If the material is manufactured, talk with your CO consultant and what kind of impact could have different routings, BOM and prices of raw materials between plants. Same considerations for valuation of stocks and margin.
Finally, in the page 10 of the document you can read
Valuation must be at Plant level in the following cases:
u2022If you want to use the application component Production Planning (PP) or Costing
u2022If your system is a SAP Retail system
I hope this helps you
Regards
Eduardo
PD: I forgot, talk this with the CFO of the company, taking in account the restrictions (when it must be plant level).
Edited by: E_Hinojosa on Nov 23, 2011 9:23 AM
Edited by: E_Hinojosa on Nov 23, 2011 9:24 AM

Release Strategy @ Company Code Level

Hi Guys:
We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
with Characteristics as Company Code ,PO Document Type and PO Value?
Thanks
Sweth

Hi
For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
The characteristics for release strategy for external purchasing documents are
Plant                - WERKS
Pur.group        - EKGRP
Pur.org            -EKORG
Acc.assignment category-KNTTP
Document value-GNETW
Document type-BSART
The table is CEKKO
Thanks

Client level , company code level , chart of account level

Hi experts
Pls expline me which are we define under client level , company code level and COA level
like :
1) field status variant:
2) Dunning procedure:
3) document types:
4) doc.number range:
4) posting periods variant
5) controlling area
6) account groups
7) vendor/cust master data
8) dep key
9) chart of dep area
10) like...............................
get points
Geeta

hi geeta,
ClientA Client is the highest unit within an SAP system and contains Master records and Tables. Data entered at this level are valid for all company code data and organizational structures allowing for data consistency. User access and authorizations are assigned to each client created. Users must specify which client they are working in at the point of logon to the SAP system.
A CompanyA Company is the unit to which your financial statements are created and can have one to many company codes assigned to it. A company is equivalent to your legal business organization. Consolidated financial statements are based on the companyu2019s financial statements. Companies are defined in configuration and assigned to company codes. Each company code must use the same COA( Chart of Accounts) and Fiscal Year. Also note that local currency for the company can be different.
Company CodesCompany Codes are the smallest unit within your organizational structure and is used for internal and external reporting purposes. Company Codes are not optional within SAP and are required to be defined. Financial transactions are viewed at the company code level. Company Codes can be created for any business organization whether national or international. It is recommended that once a Company Code has been defined in Configuration with all the required settings then other company codes later created should be copied from the existing company code. You can then make changes as needed. This reduces repetitive input of information that does not change from company code to company code as well as eliminate the possibility of missed data input.
Business Area Business Area is optional and is equivalent to a specific area of responsibility within your company or business segment. BA (Business Area) also allows for internal and external reporting.
Another configuration requirement for set-up in SAP are the Basic settings consisting of the following:
Chart of Accounts(COA)
Fiscal Year Variants.
Currencies
The COA(Chart of Accounts)
The COA(Chart of Accounts) lists all General Ledger accounts that are used by the organization. It is assigned in configuration to each company code and allows for daily General Ledger postings.
Fiscal Year configuration
Fiscal Year configuration is a must and can be defined to meet your companyu2019s reporting periods whether Fiscal (any period combination that is not calendar) or Calendar( Jan-Dec).
Posting Periods are defined and assigned to the Fiscal Year.
Within the periods you specify start dates and finished dates.
SAP allows for 12 posting periods along with specially defined periods that can be used for year-end financial closing.
Rohit Agrawal

Client level, chart of accounts level, company code level

Generally what are the areas under client level, chart of accounts level, company code level.
For Ex. document types are client level, number range company code level
like the above does we have any list which is falling in the above levels.

1. Generally during customising when co code data is not asked , then settings are client level.
Country, Currency, Document types, all variants of diff types, chart of accounts, etc
2. Every master is having data - General data level (client level) for use by all co codes, Co code data level(basically for accounting purposes) and so on.
These are applicable to GL, Vendor, Customer, Asset, Matlerials, etc
For particular application we have more information at another object level also- Vendor- Purchasing, Customer-Sales, materials-Plant- controlling, etc
3. Chart of accounts level assignments are done for all automatic posting definitions-which is applicable to all company codes which are using same chart of accounts.
4. In material setting- valuation can be grouping level, co code level or plant level as these are related to costing and product costing.
Hope the above will give some idea.
In the above nothing is written about CO as you have not asked-

MDS Code Level for UCS FC Port Channel/Trunking

What is the required MDS code level needed to support FC Port-Channeling/Trunking on a 9222i, 9148, or 9509/9513 w/ Gen2 line cards to UCS 1.4(3)?
I know the fport-channel-trunk feature is needed and was released in MDS 4.2 code but I have seen documents that this level of code wont support these features when used to connect to Cisco UCS.
Can someone confirm? Is NXOS 5.0(4) or higher required?

Doug,
I wrote the doc almost a year ago and it doesn't have the latest interop matrix support information. The current MDS NX-OS support is located in this doc: http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/intmatrx.html
While, I wish this was also duplicated in UCS docs, they are more or less taking the stance that 3rd party (Cisco MDS is this case) interop is maintained by the 3rd party. EMC, Netapp, or even Cisco.
It would be a nightmare updating UCS docs with 3rd party qualifications and support.
The short answer to your question is:
UCS 1.4(1), 1.4(2), 1.4(3) Is supported by MDS9000: 3.3(4a), 3.3(5), 4.2(1a), 4.2(1b), 4.2(3a), 4.2(5), 5.0(1a), 5.0(4), 5.0(4c)
NPV was introduced in MDS 3.3. f port-channel/trunk was introduced in MDS 4.2.
As Ram mentioned above, 4.2(5) is what I would recommend if I wanted to implement f port-channel and/or f port-trunk. I have also had recent experience with 4.2(5) and it worked great with a large UCS f port-channel/trunk implementation
The specific switch limitations I mentioned in my doc still exist. Only certain models of MDS will support f port-trunk. Almost all models will support f port-channel.
Dave

Super 1.5 - source code level tracing for EJB, JSP and others

Would you want to try new installation for Super 1.6?
Please visit www.acelet.com
Thanks.
"Dominique Jean-Prost" <[email protected]> wrote:
If only your installation tool was easy to use ...
dom
"Wei Jiang" <[email protected]> a écrit dans le message news:
[email protected]...
Super supports source code level tracing for Java and JSP!
Announcement: Super 1.5 - an EJB/J2EE monitoring tool with
SuperPeekPoke
SuperLogging
SuperStress
SuperEnvironment
It is free for development.
You can anomyously down load it from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A PeekPoke tool to read/write attributes from EJBs.
* A full-featured logging/tracing tool for centralized, chronologicallogging.
* A Stress test tool.
* A global environment tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1
* Weblogic 6.0
What is new:
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView,TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView andPieView.
Changes:
1. The structure of log database changed. You need delete old installationand
install everything new.
2. The format of time stamp of SuperLogging changed. It is not localedependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clusteringenvironment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not bestopped
and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, itis
treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabasecan
be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be emptyfor
Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods willnot
try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put logdatabase
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDIname
(mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it worksfor
both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2and
1.3
Changes:
1. All changes are backward compatible, but you may need to recompilemonitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message willnot
show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: pressF1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.

"code level" document comparison software

Similar Messages

Maybe you are looking for