"Save As" extension

When I work in PSE 9 on a file and need to same it in a new format, I select "save as," change the name and select the new file type. PSE 9 used to change the file extension to match the selected file type, but now does not - although the file is formated and saved in the selected format. To change the extension, I must type in the new extension.

You have a mac, right? This is a known bug in the mac version. It happens when you open the Saving Files preference, even if you don't make any changes. The way to get around it is to quit the editor, relaunch PSE while holding down command+shift+option. Keep holding the keys till you see a window asking if you want to delete the settings file. You do. Then never go to Preferences>Saving Files again.
If you do need to change a setting in there, the only solution is to manually add the file extension when saving.

Similar Messages

Photoshop doesn't save file extension

I'm using PS cs5.1 64 bit and Bridge cs5 in Win7 Pro 64 bit.
When I "Save As", photoshop won't write the file extension unless I explicitly type it (i.e. i have to type "filename.psd" as opposed to just "filename") in the file name text box.
If I Save As the file without specifying the extension, bridge simply displays a blank page icon for the file, and if I double click it, I get the "don't know what application to use" dialog. If I select photoshop as the program to use, ps will open the file correctly.
However, even after I change the filename in bridge by adding the extension, bridge displays the PS icon, but won't preview the file (doesn't show a thumbnail).
If I want bridge to show a thumbnail, I have to re-open the file in PS, then Save As, remembering to explicitly specify the extension. THEN, Bridge will show a thumbnail.
How can I correct this? I've gone through the preferences dialog and have "save lowercase extension" checked, but this appears to be a preference for case of saved extension, not a specification that an extension should always be saved.
btw: I tried the regedit fix specified on other help forums, but this didn't help.
Thanks.

I think I figured it out.
I was saving filenames which contain "." in the name (e.g. "BO.HG.M.psd").
When I saved the file with the name "BO_HG_M", photoshop appended the .psd extension for me, and bridge is happy.
Because of the application of the images, it's important that we use the "." format for the names, so I'll just live with it and try to remember to type the ".psd" on the end.

Under Save as, extension does not match format chosen (ie, if I choose JPG, it gives my file a IIF e

Under Save as, extension does not match format chosen (ie, if I choose JPG, it gives my file a IIF extension. I have to choose JPEG 2000 to get JPG, all are off by one position)

Did you install plug-ins from a previous version of Photosop (or point the additional plug-ins to a previous version)? Photoshop CS6 has changed the location and way of installing plug-ins. All required plug-ins are stored internally–the location depends on the OS–and only non-Adobe 3rd party plug-ins should now be installed in the main Plug-ins folder.
You'll need to clean out and/or fix your plug-ins to get the correct behavior back...

Can't save png extension anymore, Save As Type is blank, already reset and uninstalled?

Before I was able to Right Click > Save Image As and it would give me the extensions as a drop down menu.
Now it shows a blank Save As dropdown bar if I try to save .pngs, and the only other thing I can select is Save As > All Type. I already tried a full uninstall, resetting firefox and starting in Safe Mode and they all have this issue. IE can download .pngs no problem.
Everything was working since yesterday.

Hello,
I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution more easily.
Thank you for contacting Mozilla Support.

Photoshop will not save file extension, how do I fix?

When saving any file, Photoshop saves only the filename without the extension- i must manually add the extension in finder- nightmare! Help Chat sucks so here I am. I have uninstalled and reinstalled but it still doesn't work- any ideas??

First, make sure you have extensions visible in the OS.
Then check Photoshop's preferences and change it back to always saving extensions.

CS5, checked "save file extensions as small case letters" but still capital, why?

hi,
i installed CS5 4 weeks ago, since this time, i never got a file extension in small case letters, only capital letters ( xxx.TIF ). why?
i checked it in preferences, see enclosed screenshot... i never had this problem in CS4.
it would be important for myself, when saving files, that alle extensions are small case letters, like xxx.psd or xxx.eps
usually i rename these extensions manually, cause i am uploading final images to PC servers, which
cant recognize capital letters, i presume....

no, i am still dealing with this problem on both macs,
mac pro mid 2010 2,8 quad (24GB RAM) and my mbp 15" i7 (4GB RAM)
where i installed Photoshop CS5.
on both macs, photoshop always saves files with capital letter file extensions (xxx.TIF or xxx.PSD)
thats very annoying, as i have to manually rename the file in the finder later.
and thats for all files i create.
i really wonder, could anyone from the adobe staff please comment if it is a bug
or anything else?
thanks!

Save as extensions scrambled on PS CS6 Mac Lion

When I select save as after editing a file brouight in as a PSD or RAW file if I choose TIFF as the file type the extension appended is PNG. If I choose JPEG the extension is esd. I just updated to be sure I have the latest version. The connection between finder and photoshop doesn't seem to be working right. Another example being when I choose to open a file the menu that opens requires me first to select the type of file I want to import before it will allow me to select a file type. There is no default.

waldhaus1 wrote:
…It will be great when a plugin migrator becomes a part of the upgrade process as is the preset migrator.
It's highly improbable you'll ever see that. Plug-ins should NOT be "migrated" at all. Fresh, updated versions should be installed from the original media, through their installers or by following the 3rd-party vendor's instructions.

Thunderbird - Change default email 'save as' extension

Saving an email as '.txt' allows the content to be checked without the risk of triggering a 'nasty'. The default 'Save as' uses '.eml' but it would be handy to allow the default to be changed to '.txt' as I've never yethad cause to save an email as '.eml'.

I don't know of any way to change the default to txt, but another possibility is to install [https://addons.mozilla.org/en-us/thunderbird/addon/importexporttools/ ImportExportTools] and choose the text format from the message right-click menu.
http://chrisramsden.vfast.co.uk/3_How_to_install_Add-ons_in_Thunderbird.html

How do I print to a postscript file with InDesign CS6 without both extensions, .indd.ps?

How do I print to a postscript file without an .indd extension in InDesign CS6? I choose Print, choose a print preset from my print shop and Save. The first time I tried it was blank (the Hide Extension was checked), so I tried to save and got a dialog box that said it cannot be saved as an .indd file (duh), to choose both or .ps. I chose .ps and it was fine, but every time I postscripted it gave me this dialog box until I unchecked Hide Extension. After I did that, every time I postscript it automatically saves both extensions. Not a big deal but it is annoying. I just want it to end with .ps like it used to. Any ideas on how to fix this?
Thanks!!

I have no idea but I am incredibly curious...why are you doing this?
Printing to postscript is a completely archaic workflow. Export to PDF
instead.
Bob
TKnudt <mailto:[email protected]>
Tuesday, January 15, 2013 6:12 PM
>
How do I print to a postscript file with InDesign CS6 without
both extensions, .indd.ps?
created by TKnudt <http://forums.adobe.com/people/TKnudt> in
/InDesign/ - View the full discussion
<http://forums.adobe.com/message/4996731#4996731

Extension of generated Idocs types

hello,
does anybody knows why I can not create extension of generated (means in table EDBAS-GENERATED = 'X') idocs?
I tried to extend idoc BATMAS03 on R/3 Ecc 6 and got message:
message e099(b1) with
'Action is not possible for generated idoctypes'
In former version of R/3 4.6C it was possible to extend such IDoc BATMAS02 (generated one) without any problems.
Of course I found in program MSED5F02 in routine CREATE_EXT_STRUCTURE new (in comparison to 4.6C) extra check which protects against extension of generated IDocs, but I want to get to know what was behind that decision or how to workaround that problem.
Thanks in advance,
Marcin

Hi,
User Exits are used to populate data in new segments added and to read them
back which provides extension to existing idocs.
IDOC EXTENSIONS
SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type. Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
First, determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save. Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
Pls reward helpful points.
Regards,
Ameet

Batch Folder Save

This photoshop is making my head hurt. I do not want to get a degree in nuclear biology in order to get the red eye out. So I don't use it, I use an ancient photo deluxe business 1.0 or something. It understands I am an idiot, and is cool with that.
Then I have this whole folder of 116 files. It said they were jpg but would not open in ancient adobe. I tried my portable CS5 thing and went into File, automate, batch. It made me hit save for each one, and saved each one as a pdf file, which I didn't want, and that folder I can open in my ancient adobe, but I cannot blur or clone unless I save it as jpg and then open again.
So all I want is to change this folder of PDF to JPG
I searched here, downloaded a script somebody said to get, opened it and realized I don't know what it is or what to do with it, and deleted it. Searched some more, learned all about similar stuff. I tried again.
What I don't understand is that one of the choices I can make near the top is to save as PDF, but there is no save as JPG. It keeps telling me to save an extension for destination but won't let me type jpg in there.
Would some one please tell me step by step, in the batch dialog, what do I do to have it convert these PDF to JPG, without me having to "save as jpg" each one.
I have 3 rows of:
Document name + extensions
But it doesn't say which on is the save to destination, and won't let me type jpg or .jpg and my head is hurting.

function(){return A.apply(null,[this].concat($A(arguments)))}
Lisa Denton wrote:
I tried my portable CS5 thing
Can you go into more detail about what you mean by "portable CS5 thing"?
I've been hearing this term a lot lately, and some have implied it's pirated software.
I'm not accusing anything, but I'd genuinely like to know what you mean by "portable".
-Noel

Setting "Append file extension" in PSE9 Trial

I downloaded the trial version, and when I open a RAW file and then go to save it, the .MRW (yes, I know that's old now!) stays in place and I have to type in the required extension, even though I have set the option in the box below. Looking at the Preferences dialogue box, I tried to set this to 'Always', but note that it always defaults back to 'Never'. This is annoying, because I don't want to overwrite my RAW files. If anyone has upgraded to the full version yet, I would like to know if this is a feature of the trial which might be unlocked on upgrade.
I have PSE6 & PSE8 still installed on my Mac. I much prefer to use Bridge from PSE8 rather than the frankly awful (and pointless) Organiser.

Barbara,
Thanks for the link, I've passed it off to the engineers to chew on.
Michael,
The specific file that carries the seed of this bug is "Adobe Photoshop Elements 9 Prefs.psp" in Users/[User Name]/Library/Preferences/Adobe Photoshop Elements 9 Settings. Trashing/renaming this file while PSE is closed will fix this particular bug. No other files need be removed. I plan on taking a closer look at this file to see what might be done.
Byard,
I am using the same version of the software that everybody else gets. Actually, I never got the beta to install on my Mac (Windows worked fine). I think there might have been a hiccup with the first attempt at the install, because I cleaned my machine of all traces of PSE9 before installing the final release version and that installed without issue. I suggest the same for anybody else that had their system touched by the beta. I don't know if that explains any of the issues you are seeing. Because I can change any preferences besides the Saving Files without issue.
This same behavior does not happen on the Windows side, mainly because this is not an option on the Windows side. You ALWAYS save an extension with Windows, that's just how the OS works. Windows reads a lot of book covers, and by that I mean it puts a lot of stock into the extension. It determines how Windows will treat the file. For Mac, an extension isn't needed, it's really there to make you feel more comfortable and to be more compatible with Windows. Mac reads the file for information about what applications it belongs to. Windows see .JPG and it has one response to that when you double click on it (this is called file association). On Mac, depending on where that particular JPEG file came from and what you've been doing with it will determine how it will be treated in the future.
-Brett

Cannot Install Android Extension

I'm trying to install the android extension flashpro_extensionforair_p1_102510
following AIR for Android - Part 1 - In this first tutorial I show you how to setup your development environment with Flash CS5.
http://http://www.gotoandlearn.com/play.php?id=123
Ive downloaded and save the extension to my desktop i double click the file to run the install it loads the adobe extension manager and it loads installing after a few Min's it times out and gives me an error message
This extension can not be installed, it requires Flash version in range of inclusive between 11 and 11
Ive tried google this error and cannot find a simple fix just wondering if some one can advise me on how to fix this so i can build my first android flash app

Hello,
That's an odd error, and one I haven't seen before. You didn't mention which platform you were using, and I just tried this on my Mac with Flash CS5 (patched to the latest version) and it worked as expected.
Here are a couple of things to try. First, check out this post, there's a link to a youtube video that describes how some people were able to work around installation issues. Secondly, I would also suggest posting in the Flash Exchange Extensions forum or the Flash General forum and see if anyone else has encountered this error.
Hope this helps,
Chris

How to obtain extensive connection logs?

Hi,
just recently I had some trouble connecting to my mail server, while determining the error I was wondering if (or where) Apple Mail saves some extensive logs about recent connections.
Mail showed a popup with a short report ("+relay not permitted at mail.mydomain.com+"), but I was unable to find a logfile containing this connection attempt. /var/log/mail.log was useless for me and I couldn' find any further logs for Mail.
Is there any chance to log the sever requests and responses, something like:
[13:53:09] C: Connected to mail.mydomain.com, port 25
[13:53:09] S: 220 mail.mydomain.com ESMTP Exim 4.63 Sat, 20 Oct 2007 13:53:16 +0200
[13:53:09] C: EHLO MAC
[13:53:09] S: 250-mail.mydomain.com Hello 010203.dsl.macdsl.com [17.112.152.32]
[13:53:09] S: 250-SIZE 52428800
[13:53:09] S: 250-PIPELINING
[13:53:09] S: 250-AUTH PLAIN LOGIN
[13:53:09] S: 250-STARTTLS
[13:53:09] S: 250 HELP
[13:53:09] C: MAIL FROM:<[email protected]> SIZE=448
[13:53:09] S: 250 OK
[13:53:09] C: RCPT TO:<[email protected]>
[13:53:09] S: 550 relay not permitted at mail.mydomain.com
[13:53:09] C: RSET
[13:53:09] S: 250 Reset OK
[13:53:09] C: QUIT
[13:53:10] S: 221 mail.mydomain.com closing connection

David Gimeno Gost wrote:
Also, Mail comes with a Turn On Logging AppleScript that I haven’t tried either, but that was discussed some time ago in the following thread:
MAIL LOG???
Excellent, that script did the trick.
Thanks for your help.
In case someone is interested, the output to console.log is similar to the format in my original post, maybe a bit more complex.
Sample from console.log
CONNECTED Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
READ Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
220 mail.mydomain.com ESMTP Exim 4.63 Sun, 21 Oct 2007 06:35:13 +0200
WROTE Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
EHLO [127.0.0.1]
READ Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
250-mail.mydomain.com Hello 010203.dsl.macdsl.com [17.112.152.32]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
WROTE Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port 25 -- socket:0x16acb770 -- thread:0x12e7d90
READ Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
235 Authentication succeeded
WROTE Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
MAIL FROM:<[email protected]>
READ Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
250 OK
WROTE Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
RCPT TO:<[email protected]>
READ Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
550 relay not permitted at mail.mydomain.com
WROTE Oct 21 06:35:15[kCFStreamSocketSecurityLevelNone] -- host:mail.mydomain.com -- port:25 -- socket:0x16acb770 -- thread:0x12e7d90
QUIT

Extension of BASIC IDoc

Hi,
can any body tell me , what are the steps of BAsic IDoc extension,
Regards,
Bhaskar

Hi..
These are the Steps to Enhance IDOC Type:
IDOC EXTENSIONS
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
First, letâs determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX .Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX .
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application. It may be necessary to enhance an ALE function module even in situations where an IDOC extension has not been performed if the IDOC data being passed to and from the application requires modifications. The following approach applies to both situations.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
The point in the ALE function module where the function exit occurs
The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Reward if Helpful.

"Save As" extension

Similar Messages

Maybe you are looking for