Restricting acknowledgments in idoc to file
hi
while restricting acknowledgments in idoc to file....
which port and client we need to mention in IDX_NOALE report.
sender port -
R/3 port or XI port ? and which client (R/3 or XI)? ...
Abhijit
Hi,
Check this
http://erpgenie.com/abaptips/content/blogcategory/38/72/
Regards
Seshagiri
Similar Messages
-
Reg: IDOC to File Scenario Acknowledgments
Hi All,
I have created a Asynchronous IDOC to FILE Scenario. It is working perfectly fine, files are getting generated as expected and FTPed.
But I am receiveing Acknowledgments back to ECC system from PI. I dont want any acknowledgments back to ECC.
Please advice.
Thanks & Regards,
Navneeth K.HI Navneeth,
Generally, you would not get any acknowledgement. Can u please explain abt the scenario? Have u done this woth BPM?
Thanks, -
How to suppress the Acknowledgement Error in IDOC to File scenario?
Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
TirumalHi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy -
IDOC to File Scenario. Acknowledgement help required
Hi All,
I have made a IDOC to file scenario (IDOC has business system and file has business service) which is working fine.
But In sxmb_moni of XI it says Acknowledgement not possible.
"<SAP:Stack>Unable to convert the sender service File_Receiver_BusService to an ALE logical system</SAP:Stack>"
Please explain me and send be blogs to send Acknowledgement back to R/3.
RegardsHello Rick,
"<SAP:Stack>Unable to convert the sender service File_Receiver_BusService to an ALE logical system</SAP:Stack>"
Check the Logical system name in SLD and in ID's Service->AdapterSpecific Identifies matches are not, go through the following link for step by step prcedure.
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Check this for providing Acknowledgments.
https://wiki.sdn.sap.com/wiki/display/ABAP/HandlingIdocAcknowledgements
Regards,
Prasanna -
Getting Receiver Agreement issue in IDOC to File scenario
Hi Gurus,
Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
Error Message:
No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
Error Category : Outbounding
Error ID : CO_TXT_OUTBINDING_NOT_FOUND
My IR design:
Sender:
Interface : VEND_IDOC_OUT_MI
Message Type : CREMDM.CREMDM04
Receiver:
Interface : VEND_FILE_IN_MI
Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
My ID Config:
1. Sender / Outbound Message: Service Type --> Business System
Service ---> SAPERP
Interface--> VEND_IDOC_OUT_MI
Adapter Type : IDOC
2. Receiver / Inbound Message: Service Type --> Business Service
Service --> IDOC2FileReceiver
Interface ---> VEND_FILE_IN_MI
Adapter Type--> File
3. In Sender Agreement : Specified the Sender Communication Channel
VEND_IDOC_OUT_Channel
4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
Can anyone help me identifying what's going wrong. I'm very new to XI and basically this is the first assignment I'm working on.
Regards,
SubhadipHi Babu,
In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
Please find the XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
<xsd:complexType name="VEND_FILE_DT">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8f584d80456311dccd680018fe79f69b
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb0390c11dc843000188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb4390c11dc84e800188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor name4
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb5390c11dcbe3400188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor City
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
a8653cb6390c11dc896100188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor PO Box
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4811db0335fd11dc9e9600188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor House No & Street
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4811db0435fd11dc98b000188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor Postal Code
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4811db0535fd11dc870500188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Vendor Country
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
7ca8d600403b11dcc9bd00188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Tax Number 1
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7040e611dcce4300188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Telephone number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7140e611dc8f3900188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
VAT Registration Number
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7240e611dccef700188bd09370
</xsd:appinfo>
<xsd:documentation xml:lang="EN">
Account Number of Vendor or Creditor
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9abaee7340e611dcb3bc00188bd09370
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="0" />
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema> -
IDOC to File --- Error occurred during back-routing Error in communication
Hi All,
I am doing a IDOC to File (File Content Conversion) Scenario in which I have mentioned the field separator and end separator.. When i trigger the IDOC, i am only getting the first field value in the output. I am getting the following error
"- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>,IHS_BS</SAP:P1>
<SAP:P2>,com_IHS_B07_BS,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>"
My port and receiver are mentioned in "IDXNOALE" so that I can ignore the Acknowledgments. Please help as the error still persists..
Thanks
AnjuTry this thread:
ALEAUD not coming to SAP from XI & u0093Acknowledgment not possible" in idx5 -
Idoc to file scenario( I dont want acknowledgements )
Hi all,
where i can disble the acknowledgements in idoc to file scenario.
KiranHi,
If you want the ack..
Go throughthis steps..
go to transaction SXMB_ADM on XI SAP system
Choose Integration Engine Configuration
Select "Execute"
Choose "Specific Configuration"
choose New Entries
Select :
Category : RUNTIME
Parameters : ACK_SYSTEM_FAILURE
Current Value : 1
and save it.
The below link contains everything about IDOC acknowledgments
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
Might help you..
Regards,
vasanth -
Idoc-xi-file scenario. how to display file in html format
I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
KumarHi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar -
In idoc to file scenario, if XI system is down where do idocs pile up?
In idoc to file scenario, if XI system is down where do idocs pile up (get stuck)
what tcode can I use to reprocess it?Sender System ,Check BD87 .. you will see alll the IDOCs in Yellow state ..
You can reprocess all the IDOCs in go from there .. if only they are in yellow state ...
regards
PS -
FIle Content Conversion Problem in IDOC-XI-File Scenario
Dear All,
I am doing IDOC-XI-FILE scenario.
I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like <b>%store_code%_%current_date%_sitemaster.xml</b> , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,<b>we have to suppress the current_date node of the xml content</b> . i have tried to suppress the current_date using these <b>DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut</b> , But I am unable to suppress it Can some body provide me the details on this .
The output xml version generated by Reciever file adapter is as below :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
</ns0:MT_SITE_MASTER>
Plz provide me the code I have to write in the file content conversion .
Thanks in advance
Regards
PrabhatIf u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier. Then use the Suppress Logic for the Current Date.
So it will look like this-
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
<CURR_DATE>
<CURRENT_DATE>20051105</CURRENT_DATE>
</CURR_DATE>
</ns0:MT_SITE_MASTER>
So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
CURR_DATE.fieldFixedLengths - 0
CURR_DATE.fixedLengthTooShortHanling - Cut
And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
Hope this solves ur problem.
Regards,
Moorthy -
Error/Doubts in Idoc-XI-File scenario
Dear All,
I am doing one scenario in which DELIVERY idoc is posted from R/3 to XI and then from XI that idoc is to be sent as flat file to one local folder.
For this scenario, I have done all ALE settings and I am able to see the idoc in XI in cXML format.Now I want to sent it as flat file.
Now, for doing this I created 2 BS & 2 TS. 1 BS & TS of type Third Party for receiver & 1 BS & TS are of type Web as ABAP for sender. Then I have created one namespace in IR. I have not created any DT, MT, MI, MM becoz the structure of source and target file are same. Now, I created one IM in which I specified specified Type as "ABAP Class" & Mapping program name as one of the Z function module as specified in one of the SAP Guides.
Then in ID, I created 2 Parties ie. one for Sender & one for receiver. Sender is having a communication channel of type Idoc & receiver is having communication channel of type File. And thn further Receiver Agreement, Inetrface Determination, Sender Agreement & Receiver Agreement are configured.
In my system there is one scenario already configured which is using Delivery idoc so I have used party in my scenario for both sender & receiver.
Now, when I am sending the idoc from R/3, I am able to see cXML in SXMB_MONI but it is taking receiver as the one which is defined for the already existing scenario but not the receiver defined by me.
Can anybody guide if I have followed the correct steps & where I am doing the error.
Warm Regards,
N.JainHi ,
Plese refer the following blogs ,
IDoc to File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
You have to do all this settings mentioned in the docuemnt:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
Also can you check this weblogs on the same:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Thanks ,
Suvarna
Award pts if it helps . -
Integration server as logical system in IDoc to file scenario
Hi,
Will we configure integration server as logical system in IDoc to file scenario or the RFC destination related to the port will be suffice?
For which logical system will the outbound partner profile configured?
Regards,
Gajendra.Hello,
I feel that the RFC destination linked to the port is the key here.
Because the scenario (IDoc to File) works in both the cases:
Case 1: Used the logical system as Integration server
Case 2: Used the logical system related to the file (third party) in the SLD.
In both the above cases the RFC destination points to the integration server.
Is this the case that in the XI scenarios (where IDoc are sent) the logical system name in the partner profile is just dummy and has not much significance??
It is the port that matters and once the Idoc reaches XI the routing takes place based on the configuration in ID.
Thanks.
Regards,
Gajendra. -
While Idoc to File XI processing : data format change
Hi All,
need help.
I am processing idoc to file in a sscenario.
Here we have one field in Idoc is "Miscdata" Where we are passing one String with multiple spaces"
While this String goes to XI it remove the multiple space and make single space. I am not getting. how can I avoide.
I can not avoide it XI side. Here I am using substring to take different value from different position of the String which are fix.
Please help me in thisclosing. thanks
-
Help needed in Idoc To File Scenario
Hi Experts,
My scenario is Idoc to File.
Here my job is to convert the purchase order idoc into xml file.
In this there are three conditions.
converting the standard PO into xml file
(ii) converting the PO with serial number into xml file
(iii) converting the PO using serial number with subcontracting into xml file
so what I feel is I need to create one scenario and based on the condition that particular PO will convert into xml file.
Conditions:
if no condition is specified then it is standard PO first case
(ii) if field tdline ne space then it is PO with serial number second case
(iii) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
Please guide how to do this scenario.
IR:
1) how many data types I need to create
2) how many message types I need to create
3) how many message interfaces I need to create
4) how many message mappings I need to create
5) how many message interfaces I need to create
ID:
1) how many receiver determinations I need to create
2) how many interface determinations I need create
3) how many receiver agreements I need to create
And where to write the conditions at message mapping level or at receiver determination level.
Kindly provide solution to every point.
Regards,
Venkat.1) if no condition is specified then it is standard PO first case
2) if field tdline ne space then it is PO with serial number second case
3) if field pstyp eq 3 then it is PO using serial number with subcontracting third case.
you have to create
1. outbound ( IDOC)
2. 3 Inbound (same MT)
create 3 mapping program each for 1 condition
create 3 interface mappings
ID:
1 reveri BS.
3 Interface determinations, so 3 receiver agrement.......
you can put the condition on the mapping or in the condition tab of the interface determinations. -
Hello, please i have a file atachment field in a form on my site. I want to restrict the size of the file that can be uploaded and the type. It's a vacancy page and I want candidates to only upload doc and pdf files. I want to also limit the file size to 50mb only. How can this be done within the BC system.
Thanks.The file extension can't be trusted, like the mime-type it can be faked by a malicious user. Also this method can just be avoided altogether by anyone who has javacript turned off. Using javascript for this is not even remotely secure.
Isn't there a way to allow file uploading but specify a whitelist of filetypes (preferably checked using byte headers or some effective method) somewhere in admin?
Liam Dilley wrote:
Hey there,
You can do the file extension with jquery for example. The basic aspect of that is:
var ext = $('#my_file_field').val().split('.').pop().toLowerCase();
if($.inArray(ext, ['exe','dll','jpg','jpeg']) == -1) {
alert('invalid extension!');
So what is hapepning there is that it checks the value of the field when someone has added the file and checks the file extensiona and produces an alert but you can do as you need.
You could run this on hover of the submit button, on change of the actual file attachement field or on click of the submit button in the checks before it submits.
BC limits files to 100mb anyway so you should be ok on that front, they wont be able to be crazy uploading.
Maybe you are looking for
-
I have various groups setup up on our server with users added. When I send an email to the group the members of that group are receiving my message, so I believe I have the correct settings for group emails. The problem I'm having is that after a few
-
Hi All BB - Curve 8520 Carrier - CellC (South Africa) For the last week now I have not been receiving SMS's at all. I can send SMS's and I have confirmed that they are being received. All other services seem fine as well. It's just the SMS receiving
-
MASSPOCHANGE: Change Overdeliv. Tol. could not be effected:ME664
Hi, I am trying to change overdelivery tolerance from 5 to 0 in PO line item (Object BUS2012) thru PO MASS maintenance. After executing the T.code , system is throwing below messages Change Overdeliv. Tol. could not be effected ME664 Re
-
Problem in printing me2l report
Hi Experts, When I try to take the printout of the report me2l. I get message that system cannot print the last 8 columns of the report. Thanks, Kiran
-
Need FM or BAPI for Vendor Master Update
Hi Friends, I require a FM or BAPI to update the vendor master data, if i change the name of the vendor only that change should reflect all other data should remain the same. but ifi use VENDOR_UPDATE i have to pass all the data, other wise it will b