Modify control record and send out to external (TAMA) system using ALE

Hi All,
I have a scenario to send idoc from ECC 5.0 to 3.1R/3 and then to TAMA system (external system-through TRFC)
In the inbound process code of 3.1R/3, I have to write a custom FM to modify the control record and point to TAMA system and then send it out to TAMA system.
Has anybody got idea about this and what function module need to use for modifying the control record and send it out. Any help is really appreciated
Thanks
Ricky

Hi Ricky,
To access IDoc data and modify it in your custom FM, you could investigate the following FM's:
EDI_DOCUMENT_OPEN_FOR_PROCESS
EDI_SEGMENTS_GET_ALL
They should allow you to access the EDIDD, EDIDC tables.
The IDoc related functions are contained in the function group EDI1, it may be helpful to start from there.

Similar Messages

Modify control record and send out to external (TAMA) system

Hi All,
I have a scenario to send idoc from ECC 5.0 to 3.1R/3 and then to TAMA system (external system-through TRFC)
In the inbound process code of 3.1R/3, I have to write a custom FM to modify the control record and point to TAMA system and then send it out to TAMA system.
Has anybody got idea about this and what function module need to use for modifying the control record and send it out. Any help is really appreciated
Thanks
Ricky

Hi Ricky,
To access IDoc data and modify it in your custom FM, you could investigate the following FM's:
EDI_DOCUMENT_OPEN_FOR_PROCESS
EDI_SEGMENTS_GET_ALL
They should allow you to access the EDIDD, EDIDC tables.
The IDoc related functions are contained in the function group EDI1, it may be helpful to start from there.

IDoc Control Record and Status Record Code, where is it!!!

Hi,
Where can i see the code for generation of control record and status record of IDoc.
   Thanks in advance for your answers

hi ,
1.first create an segment with the fields u want tcode we31 relase it .
2. create an idoc and assign segment to it tcode we30.
3.crate a message type tcode we81
4.assign that message to idoc tcode we 82.
do the ale configarations .
now u can write the code in our sender system
*1.     Create parameters/select-options for input data. i.e., message type, logical system.
parameters : p_mestyp like edmsg-msgtyp default 'ZKKUMSG',
             p_logsys like tbdlst-logsys obligatory.
*2.     Create Data objects for control record, data record and database table.
data : c_segment like edidd-segnam value 'ZKKUSEG',        "Data record (IDoc)-Segment type
       c_idoctp like edidc-idoctp value 'ZKKUIDOC'.            "Control record (IDoc)-Basic type
data : begin of i_tab occurs 0,
          ZKSNO   like ZKSTD-ZKSNO,
          ZKSNAME like ZKSTD-ZKSNAME,
       end of i_tab.
data : w_itab like i_tab.
data : s_segment like ZKKUSEG.
data : i_edidd like edidd occurs 0 with header line.
data : i_control_record like edidc.
data : i_comm_idoc like edidc occurs 0 with header line.
*3.     Select the data from responding tables into internal table for a defined condition.
here you have take ur internal table
*select single zsno zsname from zkiran into corresponding fields of itab where zsno = p_sno.
*4.     create control record into internal table.
i_control_record-mestyp = p_mestyp.         "Message Type
i_control_record-idoctp = c_idoctp.         "Basic type
i_control_record-rcvprt = 'LS'.             "Partner Type of Receiver
i_control_record-rcvprn = p_logsys.         "Partner Number of Recipient
*5.     create data record into internal table.
*i_edidd-segnam =   c_segment.
loop at i_tab into w_itab.
s_segment-zksno    = w_itab-ZKSNO.                     "Application Data
s_segment-zksname = w_itab-ZKSNAME.
i_edidd-sdata     = s_segment.
i_edidd-segnam    = c_segment.
clear w_itab.
append i_edidd.
endloop.
*6.     Process ALE Service Layer using the function module MASTER_IDOC_DISTRIBUTE. It returns the corresponding IDoc No.s.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
    master_idoc_control            = i_control_record
tables
    communication_idoc_control     = i_comm_idoc
    master_idoc_data               = i_edidd
exceptions
    error_in_idoc_control          = 1
    error_writing_idoc_status      = 2
    error_in_idoc_data             = 3
    sending_logical_system_unknown = 4
    others                         = 5.
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
          with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*7.     Display Communication IDocs.
loop at i_comm_idoc.
write : / 'Communication IDoc No. is : ', i_comm_idoc-docnum.
endloop.
*8.     Commit Work.
commit work.
i hope this sample code help u .
thanks

Photoshop and elements 13 Working in iPhoto Want to edit image using photoshop elements Did the following IPhoto Preferences Advanced Edit Photos: In drop down menu chose in Photoshop Elements Also control click and chose edit in external editor Drop

Photoshop and elements 13
Working in iPhoto
Want to edit image using photoshop elements
Did the following
IPhoto>Preferences>Advanced>Edit Photos: In drop down menu chose in Photoshop Elements
Also control click and chose edit in external editor
Drop down menu edit photos in external program>photoshop Elements
Go to to the image I'm working on --- selected the image, the clicked on edit. When nothing happened I double clicked the image. Still elements didn't open. Then I opened the Elements editor, went back to iphoto and tried the entire process again. the photo still didn't open on Elements 13 for editing.
I have 3 Elements 13 books as well as looked on line--all my references say the exact same thing ---- iPhoto>Preferences>advanced>edit in external program>photoshop Elements
I uninstalled and reinstalled both iPhoto as well as Elements.
I spoke with application technical support. There appears to be nothing wrong with my copy of iPhoto. However there is no support from Adobe. I waited for over 1.5 hours for chat support several days ago, and finally gave up.

You are probably choosing the obvious file rather than the correct file as the PSE editor. The actual editor is hidden away inside the Support Files folder. The PSE file at the top level of the PSE folder in Applications is just an alias for the welcome screen and what you're describing is exactly what happens when you choose that. You want this one:

Using Gmail in iPhoto and cannot find any of my groups to email. I have at least seven or eight groups that I email, each containing over 50 addresses. Is there a way to locate my email groups using iPhoto to send out mail in Gmail? Using version 9.5.1

Using Gmail in iPhoto and cannot find any of my groups to email. I have at least seven or eight groups that I email, each containing over 50 addresses. Is there a way to locate my email groups using iPhoto to send out mail in Gmail? Using version 9.5.1 (902.17) OS is Mavericks 10.9.1.

Your question and description is not very clear to me, so hopefully something here will help:
1. Gmail is a service not an app or a place. So you need to access the service with an app - that can be iPhoto, Mail, Outlook or any other mail client, or even a Web Browser like Safari or Firefox.
So you can't "go to GMail" as you write, but instead you go to an application set up to use the GMail service.
2. iPhoto is not a mail client. It's a handy way to email pics to Grandma, but for what you're doing you need to use an app that supports all of the Gmail service. iPhoto doesn't. There is no way around that.
3. How to send to groups will vary depending on what app you use to access the GMail service. All of these apps can receive photos from iPhoto, either - as in the case of Mail and Outlook, via the Share function - or, in the case of all the rest - via a Media Browser.
For help sending to Groups using any of these other apps you need to ask omn their respective forums. But the workflow is quite simple:
Using Mail or Outlook set in the iPhoto Prefereneces:
1. Select the pic(s) you want to share.
2. Choose email from the Share function
3. Make your selections re size etc
4. The email opens up in Mail or Outlook
- from there you need to figure out how to use the email client.
Using any other app:
1. In the mail app create a new email
2. Click on the Attach button or link
3. Use the Media browser to select the pic(s) you want to send
4. Attach them
- from there you need to figure out how to use the email client.
For help accessing your photos in iPhoto see this user tip:
https://discussions.apple.com/docs/DOC-4491

Find the service which controls agent on job server and find out the login it's using ?

How do I find the service that's controlling my SQL server agent on the job server and find out the login it's using ? Is there a query for this ?

Go to SQL Server Configuration Manager and you will see the SQL Server Agent service there with all the information you need.
Programmatic way:
http://stackoverflow.com/questions/7324407/get-service-account-details-of-the-sql-agent-service
Kalman Toth Database & OLAP Architect
IPAD SELECT Query Video Tutorial 3.5 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Link between control record and infotype 0003.

Hi all,
Can anybody explain me, what is the link between control record and infotype 0003?
Thanks & Regards,
Lucky.

Hi,
Control record is a heart of payroll area(pa03)
Conrtol record alswa based on payroll area where it determines the current payroll period for the exact date
It defines the payroll past for retro active accounting recongnation.
It lock the master data and teh time data to prevent changes from being made during the payroll run, this lock is valid for the paryroll past and the payroll present changes with effect the future can still be made.
It determines the earliset retrocatice a/cing period.
In simple control record is to control the payroll status of the employee
Payroll Status:(IT 0003)
The Payroll Status infotype (0003) contains data for Payroll Accounting and Time Evaluation.
The system automatically creates this infotype when the employee is hired. In general, the system updates the infotype and writes the changes to the payroll past.
You can change the payroll status of an individual employee using Payroll/Retroactive Accounting and Time Evaluation.
Thanks
Vibin

Texts go into MMS and when I text someone it adds the recipient twice and sends out 2 texts.

I am having a problem after downloading the verizon update 10.1.0.4189 all texts go into MMS and when I text someone it add the recipient twice and sends out 2 texts. Anybody have this issue and any luck resolving?

Just found this thread: http://supportforums.blackberry.com/t5/BlackBerry-Q10/Text-messages-being-sent-switched-to-MMS-and-b... If anyone here's that this resolved, I'd love to know. Thanks!

How to send sapmails to external mail systems

Hi,
how to send sapmails to external mail systems....
like if we want to mail a purchase order from SAP System to *@yahaoo.com or @.com.
TY.

hi manish,
u can do it.
chk this .
chk this code
DATA: objpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE.
DATA: objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE.
DATA: objbin LIKE solisti1 OCCURS 10 WITH HEADER LINE.
DATA: objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE.
DATA: reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE.
DATA: doc_chng LIKE sodocchgi1.
*& Form f_send_mail
text
--> p1 text
<-- p2 text
FORM f_send_mail .
*store the vendor name, vendor email id , employee name and employee
*email id in the internal table int_crb
Creation of the document to be sent
CLEAR doc_chng.
REFRESH objpack.
REFRESH objhead.
REFRESH reclist.
REFRESH objtxt.
File Name
doc_chng-obj_name = 'SHIPMENT'.
Mail Subject
CONCATENATE 'Shipment Document No.' int_crb_mail-shipdocnum
'Cleared.'
INTO doc_chng-obj_descr SEPARATED BY ' '.
Mail Contents
objtxt-line = 'Hi,'.
APPEND objtxt.
objtxt-line = ' '.
APPEND objtxt.
CONCATENATE 'Shipment Document Number ' int_crb_mail-shipdocnum
' cleared for move.' INTO objtxt-line SEPARATED BY ' '.
APPEND objtxt.
objtxt-line = ' '.
APPEND objtxt.
CLEAR objtxt.
objtxt-line = 'Regards '.
APPEND objtxt.
objtxt-line = ' '.
APPEND objtxt.
objtxt-line = 'SAP '.
APPEND objtxt.
CLEAR objtxt.
APPEND objtxt.
DESCRIBE TABLE objtxt LINES tab_lines.
READ TABLE objtxt INDEX tab_lines.
doc_chng-doc_size = ( tab_lines - 1 ) * 255 + STRLEN(
objtxt ).
Creation of the entry for the compressed document
CLEAR objpack-transf_bin.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = 'RAW'.
APPEND objpack.
Completing the recipient list
target recipent
CLEAR reclist.
reclist-receiver = int_crb_mail-empperid. "employee email ID
"wf_empperid.
reclist-express = 'X'.
reclist-rec_type = 'U'.
APPEND reclist.
copy recipents
CLEAR reclist.
reclist-receiver = int_crb_mail-smtp_addr."vendor email id
reclist-express = 'X'.
reclist-rec_type = 'U'.
reclist-copy = 'X'.
APPEND reclist.
Sending the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = doc_chng
TABLES
packing_list = objpack
object_header = objhead
contents_bin = objbin
contents_txt = objtxt
receivers = reclist
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
operation_no_authorization = 4
OTHERS = 99.
COMMIT WORK.
SUBMIT rsconn01
WITH mode = 'INT'
WITH output = ' '
AND RETURN.
ENDFORM. " f_send_mail
for any clarifiaction pls mail me.
pls reward points, if this helped u.
regards,
anversha.
[email protected]

The button on my Ipod Touch (the big one just below the screen) will not work when I press it. Nothing happens, when before it would wake my IPod out of sleep mode, and exit out of programs I was using. Now, no reactions. What should I do?

The button on my Ipod Touch (the big one just below the screen) will not work when I press it. Nothing happens, when before it would wake my IPod out of sleep mode, and exit out of programs I was using (ex. ITunes or Safari to main screen) . Now, no reactions. When I press the button, it appears to be more indented then it was before. What should I do? Do I need to get it fixed or replaced, or is this a problem I can fix on my own? Whatever it is, I really need some advice. Thanks in advance.

Try:
fix for Home button
iPhone Home Button Not Working or Unresponsive? Try This Fix
- If you have iOS 5 and later you can turn on Assistive Touch it add the Home and other buttons to the iPods screen. Settings>General>Accessibility>Assistive Touch
- If not under warranty Apple will exchange your iPod for a refurbished one for:
Apple - Support - iPod - Repair pricing
You can do it an an Apple store by:
Apple Retail Store - Genius Bar
or sent it in to Apple. See:
Apple - Support - iPod - Service FAQ
- There are third-party places like the following that will repair the Home button. Google for more.
iPhone Repair, Service & Parts: iPod Touch, iPad, MacBook Pro Screens

Create and send an email as a delegate using EWS Managed API

Hi All,
I would like to create and send an email as a delegate using EWS Managed API for that i have crated one user as a delegate to that mailbox owner.
after adding user as delegate, when i try to create an email The EmailMessage class taking only FolderId as parameter but not taking Mailbox object as parameter. But in web reference they said that EmailMessage taking FolderId and Mailbox object as parameter.
EmailMessage message = new EmailMessage(service);
message.Subject = "Company Soccer Team";
message.Body = "Are you interested in joining?";
message.ToRecipients.Add("[email protected]");
message.Save(new FolderId(WellKnownFolderName.Drafts, new Mailbox("[email protected]")));https://msdn.microsoft.com/EN-US/library/office/dn641963(v=exchg.150).aspx#bk_createewsmacould you people please help me on this?ThanksNaresh

Thanks for reply glen.
I have added delegate using Add-MailboxPermissions. Now i am able to save an email in mailbox owner drafts
folder.
Glen,
I have a one more question.(I am using EWS Managed API).
I(owner) have shared my calendar(eg. samplecalenderfolder) with another user(delegate) (i.e.,he is the
delegate of my mailbox) and i have given only permission to the this folder(samplecalenderfolder)
only and the permission level is Reviewer.
if i login with user(i.e.delegate) i am not able to get the shared calendar folders(i.e.,samplecalenderfolder)
that what i a have shared.
below is the code snippet i am using to get the calendar folders.
Folder folder = Folder.Bind(service,WellKnownFolderName.Calendar);
FindFoldersResults addtionalFolders = service.FindFolders(folder.Id, new FolderView(10));
could you please tell us how to get the shared calendar folders.
Thanks
Naresh

Setting Up Mailserver to received and Send Mail for external Network

I have a G5 currenty running 10.3.9 Server with Mail services run and working fine, we are upgrading to 10.4 Server and would like our Sales Reps the ability to send and Receive mail from outside the office. How do I configure my server, Router, ISP and/or Mail clients to do this??? we are currently able to recieve mail from outside just not send.

I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
# Global Postfix configuration file. This file lists only a subset
# of all 250+ parameters. See the sample-xxx.cf files for a full list.
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# sample-smtpd.cf).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see sample-local.cf).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# $inet_interfaces, while $local_recipient_maps is non-empty and the
# recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#unknown_local_recipient_reject_code = 550
unknown_local_recipient_reject_code = 450
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in file sample-smtpd.cf.
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions restriction in the
# file sample-smtpd.cf for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction in the file sample-smtpd.cf.
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = gateway.my.domain
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 50 SMTP server process
# limit, this limits the mail inflow to 50 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# Insert text from sample-virtual.cf if you need virtual domain support.
# "USER HAS MOVED" BOUNCE MESSAGES
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.
# TRANSPORT MAP
# Insert text from sample-transport.cf if you need explicit routing.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination
# and unknown@[$inet_interfaces] is returned as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see the sample-filter.cf file.
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#fast_flush_domains = $relay_domains
#fast_flush_domains =
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 10
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you don't have X installed on the Postfix machine, try:
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
# THE FOLLOWING DEFAULTS ARE SET BY APPLE
# bind to localhost only
inet_interfaces = all
# turn off relaying for local subnet
mynetworks_style = host
# mydomain_fallback: optional domain to use if mydomain is not set and
# myhostname is not fully qualified. It is ignored if neither are true.
mydomain_fallback = localhost
myhostname = jamestownpress.com
mailbox_transport = cyrus
enable_server_options = yes
luser_relay =
maps_rbl_domains = dun.dnsrbl.net
message_size_limit = 0
mydestination = $myhostname,localhost.$mydomain
smtpd_use_tls = no
smtpd_enforce_tls = no
smtpd_tls_loglevel = 0
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = plain
server_enabled = 1
relayhost =
smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
always_bcc =
mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
content_filter = smtp-amavis:[127.0.0.1]:10024
so what do I need to change

Problem in modifying control record

Hi All,
My scenario is Purchase order to Sales order. Once PO is created IDOC will be created and that idoc will be taken as source and i will be modifying the idoc in abap mapping as per requirement.
All the segements are being modified and getting updated in IDOC but when i am trying to change the control record its not getting reflected in the r/3 but when i check in moni before comming to r/3 the xml struture has changed as per my requirement even for control record also but while comming from XI control record is not getting changed.
I would like to change senderpartner and sender partner type in control records.
every configurattion steps has been done correctly.
Would request your experiences if you would have faced any this type of situation in your projects.
Thanks in Advance.

Apply Control Record Values from Payload
If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values.
http://help.sap.com/saphelp_nw04s/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm

Configure/create condition records to send out copy of PO to vendor

Hello,
I am trying to create a condition record / or configure the system with the objective to send out the PO copy automatically, either in pdf or doc format, to the vendor on saving the PO. Please help in the set up of the same with the steps or idea on how to do it.

hi
You need to do some configuration for this.
u2022     Go to NACE.
u2022     Select EF and click on OUTPUT TYPES.
u2022     Then select Output Type NEU and click on processing routines .
u2022     In that you have to add a new entry - medium 5 .
u2022     Then you need to assign a program, form routine and form.
u2022     You can use the standard program i.e. SAPFM06P, FORM routine is always ENTRY_NEU and standard MEDRUCK.
u2022     Then in PARTNER FUNCTION you need to add a new entry : medium - 5 and function - VN .
u2022     For subject of the mail go to Mail Title and Texts. In title give PO No. &EKKO-EBELN& .
u2022     Under General data -> Replacement of text symbols give programme as SAPMM06E and Form Routine as TEXT_SYMBOL_REPLACE.
u2022     Now the subject will be PO No. 1800004202.
u2022     You need to maintain your email id in tcode SU01 and also the vendor's email id.
u2022     Now while creating a new purchase order , change the medium to External Send .
u2022     Then goto Communication Method and select CS01. ALSO make sure that the Cover Page Text has value PO No. &EKKO-EBELN& .
now in further data select send immidiately
now save and chck ur output message in transaction SOST
u2022     Use note no 191470

IDOC control record mapping - Sender Partner number defaulted to log. sys.

My PI scenario is file to IDOC scenario.
I have ticked "apply values from payload" checkbox, so Sender Partner Number is being defaulted to logical system assigned to my business system.
Logical system name has to be unique in PI. My understanding is that I can not have more than 1 business system with the same logical system assigned to it.
In SAP, I need to have idocs, coming from different businees systems through PI, set to have the same sender partner number,
which is not possible when "apply values from payload = 'X' and messages are coming from different business systems.
Calling all PI Gurus, have you got a workaround ?

Hi,
Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
In SAP ECC you need to have this logical system ...to process the received idocs..
thats it... Hope you got
Regards
Rajesh

Modify control record and send out to external (TAMA) system using ALE

Similar Messages

Maybe you are looking for