Contract partner in ISU to be created as Customer in SD

Dear Experts
I am able to Created Contact partner , Contract account etc
But the Contract partner created is not reflected automatically as Customer in SD
So what could be the reason and what are the required configurations to be done
Thank you in advance
warm regards
narasimha
Edited by: NarasimhaMS on Nov 18, 2009 12:05 PM
Edited by: NarasimhaMS on Nov 18, 2009 12:07 PM

Hi
If ur system is a perfect customised system u need to just assign a reference partner created in XD01 and assign it in FPP1 while creating a BP under " Identification " tab under reference partner field.
u may get help from a sd consultant for creating a sold to party customer in xd01 assign that customer in fpp1 or fpp2
but the prerequisite is that u need a long setting to be maintained for making the sd customer getting viewd in isu
kr
raj

Similar Messages

Generate Welcome Letter for Business Partner in ISU?

Hi Experts,
Welcome Letter to be generated, when a new business partner is created using FPP1 Tcode.
If I created a Business Partner, so the system automatically will generate a welcome letter for the partner in ISU.
How to do it?
Thakns in advance.
Sekhar

Hi,
you can use event 1052 to create the correspondence container we a BP is created. I don't think there's any customizing for that. You create a correspondence type ZBPC in:
Financial Accounting > Contract Accounts Receivable and Payable > Basic Functions > Correspondence > Define Correspondence Types
the you assign a print form to the correspondence type:
Financial Accounting > Contract Accounts Receivable and Payable > Basic Functions > Define Application Forms for Correspondence
an in you event you call functions:
FKK_GET_CORR_CUSTOMIZING - Read correspondence type customizing
FKK_CREATE_COKEY - If you need to create a cluster of data due to performance reason whe you fill data that it's not possible to put in DFKKCOH or DFKKCOHI. If you do taht you'll need to do somthing like:
write it with the export command,
so that the cluster structure is build by that command.
EXPORT i_zdomcluster FROM i_zdomcluster
         TO DATABASE dfkkcodclust(co)
         ID w_cokey.
Pick it up again, access with relid for index use
SELECT * FROM dfkkcodclust INTO TABLE i_dfkkcodclust
           WHERE relid = c_relid_co
           AND   cokey = w_cokey.
And then you call function module FKK_WRITE_CORR to create you correspondence container.
FPCOPARA will do the rest...
I use this to create direct debit letters when a customer account changes to ask the customer to go to the bank and request to chage hsi domiciliation details.
Cheers,
Adriano.
PS: Some answers on this forum seem to be done by people that don't even understand simple questions???
Edited by: Adriano Silva on Sep 12, 2008 10:56 AM

Difference between Business Partner (General) and Contract Partner

Hi,
How is a business partner different from a contract partner with respect to IS-U?
Thanks
C

General Business Partner:
      The general business partner is only stored for information purpose.
Contract Partner
     A contract partner is linked to the company through contract accounts and contracts. This makes
     you to possible to allocate contract account to a business partner and bill for services if the
     business partner was created with the role contract partner.
Please Allot points if it helps
Please let me know if you need any more clarifications on this.
Regards,
Shiva Kumar

Partner Role not coming when creating the Vendor Master

Hi all
There is a standrd role AZ.
There is a standrd Partner Determination procedure L1.
The role AZ is assigned to the Partner Determination procedure L1.
When creating the vendor master in MK01 the role is not coming in the list of partner function.
For Document types there is a standard shema 0002.
The role AZ has also been assigned to doc type.
What can be the reason.
Is the assignment against doc type at all required.
Please suggest.
Regards

The procedure for setting partner functions:
Step 1
Vendor Account Group
IMG->LOGISTICS GENERAL->BUSINESS PARTNER->VENDOR->CONTROL ->DEFINE
ACCOUNT GROUPS AND FIELD SELECTION
Step 2
Defining Partner Schemas
IMG->MATERIALS MANAGEMENT->PURCHASING->PARTNER -> DETERMINATION -
>PARNER SETTINGS IN VENDOR MASTER RECORD
->DEFINE PARTNER SCHEMAS
Step 3
Assign Partner Schema
IMG->MATERIAL MANAGEMENT->PURCHASING->PARTNER DETERMINATION->PARTNER
SETTINGS IN VENDOR MASTER RECORD->DEFINE PARTNER SCHEMA
« THEN ASSIGN PARTNER SCHEMA
Step 4
Define Permissible Partner Role Per Account Group
IMG->MATERIAL MANAGEMENT->PURCHASING->PARTNER DETERMINATION -
>PARTNER ROLES ->DEFINE PERMISSION PARTNER ROLES
If you want a partner schema for your own document type then define your partner schema and assign to document type using the below mentioned path.
IMG->MATERIAL MANAGEMENT->PURCHASING->PARTNER ->DETERMINATION -
>PARTNER SETTINGS IN PURCHASING DOCUMENTS ->DEFINE PERMISSION
PARTNER SCHEMAS
And then
ASSIGN PARTNER SCHEMAS TO DOCUMENT TYPE
Once you have this configuration then you change your vendor in easy access menu (XK02-select partner function) define the partner roles.

Sending mail to the partner when the quotation is created in va21

i need to send the email to the partner when the quotation is created(va21) or changred(va22) with smart form. plese advice how can i achive this..
thanks,

Hi,
You can send by using the function module : SO_NEW_DOCUMENT_ATT_SEND_API1 . for that RSWNSENDMAIL1 is a sample program for sending mails.
Then for your requirement, find the appropriate exit/badi and put the mail send code inside that.
Regards,
Renjith Michael.

Setting required to create Business partner record in SAP GTS for the customer who transferred from the SAP ECC system

Dear Experts,
Can you please suggest me list of activities require to automatically create Business partner record in SAP GTS for the customer who transferred from the SAP ECC system .
i.e If I create the customer master record and transfer the same CMR to SAP GTS , what are the setting requires to maintain in SAP GTS sytem to automatically create the Business partner .
Ram

Hi Raghu,
Below are the main settings required to enable you to transfer Customer Master Data to SAP GTS. Please note that their is a difference between, Customer Master Record and Customer Master Data in terms of data and for GTS, we transfer Customer Master Data. Hence, below are the settings required:-
In SAP ECC system:-
Activate the change pointers for Customer Master Data apart from enabling basic connection settings.
Schedule a job to run at regular intervals to transfer all the customer master data for the available change pointers to the SAP GTS system
2. In SAP GTS system:-
Maintain the Mapping for ECC Customers to SAP GTS Business Partners in the General settings area of the SPRO in SAP GTS system
Ensure that the Number range is maintained for those GTS Business Partners.
Also, some time you may be required to maintain the organisational structure to ensure full working.
I hope this will be helpful to you.
Regards,
Aman

Failed to create executive customer (by Business Partner)

Forum,
I am having problems with a recent upgrade to 8.81 PL06. On the server when the OI addon is started it prompts the template creation screen. Upon trying to create them it comes up with the error:
Failed to create 'Executive Customer (By Business Partner)'
This is despite being a local admin hence eliminating access rights.
I have also followed instructions from SAP Note: 861055 - Missing Outlook Integration template however this was to no avail. I get the same error. Upon loading the 'Define Snapshot Templates' screen this is empty for the UK
This i suspect is what is causing 'Internal Error' message when trying to send emails on clients in addition to the fact nothing is being attached to the email.
Outlook Integration server has been reinstalled on the server too. It would seem the clients don't seem to be pick up the templates guide.
Any assistance would be greatly appreciated.
Regards,
Juan

Hi Jun,
Have you checked this: Got an error when Outlook integration create the template
Thanks,
Gordon

WCF client consumes JAVA web service - should I use WCF or just create a custom parser/message factory?

We've a business partner who requires us to create a service request message with a SAML 2.0 assertion. The partner's supplied two certificates and a test harness for their JAVA webservice.
I've created a WCF client with a `CustomBinding` to try and recreate the request and consume the service, but I'm getting so frustrated with the nuances of WCF (and the lack of intrinsic support for SAML 2.0) I'm wondering am I better off using something like
a `WebClient` or `HttpWebRequest` and encrypting/building & signing the XML web request and doing the same for the response. I know there's a lot of work involved on this but at least I'd be in full control.
Your advice would be very much appreciated, what I'm working with is displayed below
**Note: I was supplied with a SoapUI Test harness for the Java service**
**The vendor supplied me with this request (ran though SOAPUI and extracted via Fiddler)**
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
<SOAP-ENV:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsse:Security SOAP-ENV:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<xenc:EncryptedKey Id="EncKeyId-29B98C291D1FDFB39113352984774895">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>
<ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference>
<ds:X509Data>
<ds:X509IssuerSerial>
<ds:X509IssuerName>CN=test_server</ds:X509IssuerName>
<ds:X509SerialNumber>12356789</ds:X509SerialNumber>
</ds:X509IssuerSerial>
</ds:X509Data>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>

</xenc:CipherValue>
</xenc:CipherData>
<xenc:ReferenceList>
<xenc:DataReference URI="#EncDataId-3"/>
</xenc:ReferenceList>
</xenc:EncryptedKey>
<wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-29B98C291D1FDFB39113352984773591" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> </wsse:BinarySecurityToken>
<ds:Signature Id="Signature-1" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<ds:Reference URI="#id-2">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<ds:DigestValue>

</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>

</ds:SignatureValue>
<ds:KeyInfo Id="KeyId-29B98C291D1FDFB39113352984773792">
<wsse:SecurityTokenReference wsu:Id="STRId-29B98C291D1FDFB39113352984773893" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Reference URI="#CertId-29B98C291D1FDFB39113352984773591" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
</wsse:Security>
<saml:Assertion ID="_54d0c8395de26c3e44730df2c9e8d3e9" IssueInstant="2012-02-17T10:40:36.806Z" Version="2.0" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">
<saml:Issuer>CN=test_client</saml:Issuer>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<Reference URI="#_54d0c8395de26c3e44730df2c9e8d3e9">
<Transforms>
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>

</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>

</SignatureValue>
<KeyInfo>
<X509Data>
<X509Certificate>

</X509Certificate>
</X509Data>
</KeyInfo>
</Signature>
<saml:Subject>
<saml:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">[email protected]</saml:NameID>
</saml:Subject>
<saml:Conditions NotBefore="2012-02-17T10:40:21.806Z" NotOnOrAfter="2012-02-17T10:41:06.806Z"/>
</saml:Assertion>
<wsa:Action SOAP-ENV:mustUnderstand="1">http://www.xxxxxxx.xxx/ws/schemas/xxxxxx1/xxxx/xxxxxxxxxxxxxx</wsa:Action>
<wsa:MessageID SOAP-ENV:mustUnderstand="1">uuid:bffc27ba-68d9-44e6-b1f0-e2f852df7715</wsa:MessageID>
</SOAP-ENV:Header>
<SOAP-ENV:Body wsu:Id="id-2" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<xenc:EncryptedData Id="EncDataId-3" Type="http://www.w3.org/2001/04/xmlenc#Content">
<xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
<ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Reference URI="#EncKeyId-29B98C291D1FDFB39113352984774895"/>
</wsse:SecurityTokenReference>
</ds:KeyInfo>
<xenc:CipherData>
<xenc:CipherValue>

</xenc:CipherValue>
</xenc:CipherData>
</xenc:EncryptedData>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
**This is as close as I've gotten with my WCF client. Issues I can immediatley is that the `<o:SecurityTokenReference>` element should contain the Issuer and Serial, instead it contains a `KeyIdentifier` element?**
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1" u:Id="_3"/>
<a:MessageID u:Id="_4">urn:uuid:fc8ef84b-dbf5-4150-a0c3-d4cc986333d1</a:MessageID>
<ActivityId CorrelationId="a9e1fec4-32bc-4633-909e-3d601c809b3c" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">d1909115-8922-46f3-a96c-db15bf91c599</ActivityId>
<a:ReplyTo u:Id="_5">
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
<VsDebuggerCausalityData xmlns="http://schemas.microsoft.com/vstudio/diagnostics/servicemodelsink">uIDPo27oY4/3mnBOry0YL4StqvcAAAAA0UM+eVt4fU2AOe9/B3lPDZNf/2HmAuNEvzAoW0eKVSUACQAA</VsDebuggerCausalityData>
<a:To s:mustUnderstand="1" u:Id="_6">https://localhost:8089/ws</a:To>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<u:Timestamp u:Id="uuid-e5592f06-32af-40fb-996e-a0a469c7ed5e-2">
<u:Created>2012-04-24T20:41:50.447Z</u:Created>
<u:Expires>2012-04-24T20:46:50.447Z</u:Expires>
</u:Timestamp>
<e:EncryptedKey Id="uuid-e5592f06-32af-40fb-996e-a0a469c7ed5e-1" xmlns:e="http://www.w3.org/2001/04/xmlenc#">
<e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<o:SecurityTokenReference>
<o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">lU10DQn4lSpE4fRpE9gslm5QDt0=</o:KeyIdentifier>
</o:SecurityTokenReference>
</KeyInfo>
<e:CipherData>
<e:CipherValue>

</e:CipherValue>
</e:CipherData>
<e:ReferenceList>
<e:DataReference URI="#_2"/>
<e:DataReference URI="#_7"/>
<e:DataReference URI="#_8"/>
</e:ReferenceList>
</e:EncryptedKey>
<o:BinarySecurityToken u:Id="uuid-fad0c01f-ab4b-4a5f-bec6-93aa8c2d5a52-1" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"></o:BinarySecurityToken>
<e:EncryptedData Id="_7" Type="http://www.w3.org/2001/04/xmlenc#Element" xmlns:e="http://www.w3.org/2001/04/xmlenc#">
<e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
<e:CipherData>
<e:CipherValue>

</e:CipherValue>
</e:CipherData>
</e:EncryptedData>
<e:EncryptedData Id="_8" Type="http://www.w3.org/2001/04/xmlenc#Element" xmlns:e="http://www.w3.org/2001/04/xmlenc#">
<e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
<e:CipherData>
<e:CipherValue></e:CipherValue>
</e:CipherData>
</e:EncryptedData>
</o:Security>
</s:Header>
<s:Body u:Id="_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<e:EncryptedData Id="_2" Type="http://www.w3.org/2001/04/xmlenc#Content" xmlns:e="http://www.w3.org/2001/04/xmlenc#">
<e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
<e:CipherData>
<e:CipherValue></e:CipherValue>
</e:CipherData>
</e:EncryptedData>
</s:Body>
</s:Envelope>
Using this configuration for the WCF CustomBinding
<system.serviceModel>
<bindings>
<customBinding>
<binding name="WSHttpBinding_IEnquiryRequest" >
<transactionFlow />
<security defaultAlgorithmSuite="TripleDesRsa15"
authenticationMode="MutualCertificate"
messageSecurityVersion="WSSecurity11WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10"
requireDerivedKeys="false"
>
<secureConversationBootstrap authenticationMode="CertificateOverTransport"
messageSecurityVersion="WSSecurity11WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10"
requireDerivedKeys="false" />
</security>
<textMessageEncoding messageVersion="Soap11WSAddressing10" />

<httpsTransport requireClientCertificate="true" />
</binding>
</customBinding>
</bindings>
<behaviors>
<endpointBehaviors>
<behavior name="certBehaviour">
<clientCredentials>

<clientCertificate x509FindType="FindBySubjectName" storeLocation="CurrentUser" storeName="My" findValue="test_client" />
<serviceCertificate>
<defaultCertificate x509FindType="FindBySubjectName" storeLocation="CurrentUser" storeName="My" findValue="test_server"/>
<authentication revocationMode="NoCheck" certificateValidationMode="None" />
</serviceCertificate>
</clientCredentials>
</behavior>
</endpointBehaviors>
</behaviors>
<client>
<endpoint
address="https://localhost:8089/pvs/ws"
binding="customBinding"
bindingConfiguration="WSHttpBinding_IEnquiryRequest"
contract="XXXService.enquiryRequest"
name="WSHttpBinding_IEnquiryRequest"
behaviorConfiguration="certBehaviour"
>
<identity>
<dns value="test_server"/>
</identity>
</endpoint>
</client>
</system.serviceModel>
I've no idea how to insert the SAML 2.0 assertion in there before it's signed. That and the Key Issuer/serial issue above is where my main problems lie with the request.
Any and all help appreciated

Yaron,
Thanks a million for your response, think you hit the nail on the head there. Actually figured out the first part myself this morning, I've retrieved the SymmetricSecurityBindingElement object from the binding configured in the app.config and set it explicitly,
just as you've defined. Couldnt figure out how to do this yesterday for some reason! Here's the code for anyone that's interested:
//Get custom binding reference from app.config
CustomBinding binding = new CustomBinding("bindingNameInConfig");
// Reference the symmetric security element
SymmetricSecurityBindingElement securityBindingElement = binding.Elements.Find<SymmetricSecurityBindingElement>();
// Get the x509ProtectionParams from the security element
X509SecurityTokenParameters tokenParameters = new X509SecurityTokenParameters();
tokenParameters.X509ReferenceStyle = X509KeyIdentifierClauseType.IssuerSerial;
tokenParameters.RequireDerivedKeys = false;
tokenParameters.InclusionMode = SecurityTokenInclusionMode.AlwaysToInitiator;
// Set the X509SecurityTokenParameters to point to the one's just configured. This is for symetric encryption, for asymetric this line needs to change
securityBindingElement.ProtectionTokenParameters = tokenParameters;
Are you sure that SAML assertion is not signed? That makes things a lot easier! Do you think the following approach will work when inserting in the SAML 2.0 assertion? :
Create a class that inherits from IClientMessageInspector and insert the SAML as shown below
using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.ServiceModel;
using System.ServiceModel.Channels;
using System.ServiceModel.Description;
using System.ServiceModel.Dispatcher;
using System.Text;
using System.Xml;
using Microsoft.IdentityModel.Protocols.XmlSignature;
namespace TestClient.Application
class Saml20Extension : IClientMessageInspector, IEndpointBehavior
#region Implementation of IClientMessageInspector
public object BeforeSendRequest(ref Message request, IClientChannel channel)
MessageBuffer buffer = request.CreateBufferedCopy(int.MaxValue);
// ** Add the SAML Assertion XML here **
request = buffer.CreateMessage();
return null;
public void AfterReceiveReply(ref Message reply, object correlationState)
MessageBuffer buffer = reply.CreateBufferedCopy(Int32.MaxValue);
// ** REMOVE THE SAML ASSERTION HERE **
reply = buffer.CreateMessage();
#endregion
#region Implementation of IEndpointBehavior
public void AddBindingParameters(ServiceEndpoint endpoint, System.ServiceModel.Channels.BindingParameterCollection bindingParameters)
public void ApplyClientBehavior(ServiceEndpoint endpoint, ClientRuntime clientRuntime)
// Add this implementation to the inspectors.
clientRuntime.MessageInspectors.Add(this);
public void ApplyDispatchBehavior(ServiceEndpoint endpoint, EndpointDispatcher endpointDispatcher)
public void Validate(ServiceEndpoint endpoint)
#endregion
Also, There's a second signature being inserted into my WCF request that I need to replace with the SAML insertion - how do i get rid of the second signature?? (see updated request below)
POST https://localhost:8089/pvs/ws HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Host: localhost:8089
Content-Length: 6720
Expect: 100-continue
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<s:Header>
<a:Action s:mustUnderstand="1" u:Id="_3"/>
<a:MessageID u:Id="_4">urn:uuid:84dc0bb8-13fd-4e90-84c4-ed1e6e831801</a:MessageID>
<ActivityId CorrelationId="07e0df62-d40a-4e24-aacc-12e626f80e8b" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">40077c44-d415-4567-99a1-1ea610c41d94</ActivityId>
<a:ReplyTo u:Id="_5">
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
<VsDebuggerCausalityData xmlns="http://schemas.microsoft.com/vstudio/diagnostics/servicemodelsink">uIDPo1f0ZJ98FOxIvULl0pmGv/wAAAAAEGu5/G7VNkia/XbStJDa+ldqi+8xxdtAiBL+Y8vCqa0ACQAA</VsDebuggerCausalityData>
<a:To s:mustUnderstand="1" u:Id="_6">https://localhost:8089/pvs/ws</a:To>
<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<e:EncryptedKey Id="uuid-5b1de37e-ea76-4f75-b268-ebb63b554c11-1" xmlns:e="http://www.w3.org/2001/04/xmlenc#">
<e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/>
<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
<o:SecurityTokenReference>
<X509Data>
<X509IssuerSerial>
<X509IssuerName>CN=test_server</X509IssuerName>
<X509SerialNumber>123456789</X509SerialNumber>
</X509IssuerSerial>
</X509Data>
</o:SecurityTokenReference>
</KeyInfo>
<e:CipherData>
<e:CipherValue></e:CipherValue>
</e:CipherData>
<e:ReferenceList>
<e:DataReference URI="#_2"/>
</e:ReferenceList>
</e:EncryptedKey>
<o:BinarySecurityToken u:Id="uuid-d62ff21f-7e9b-460d-a0ee-d5fad221427d-1" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIBpzCCARCgAwIBAgIETzKMfzANBgkqhkiG9w0BAQUFADAYMRYwFAYDVQQDDA10ZXN0X2ZhY2lsaXR5MB4XDTEyMDIwODE0NTM1MVoXDTE3MDIwODE0NTM1MVowGDEWMBQGA1UEAwwNdGVzdF9mYWNpbGl0eTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAvzdwlxcpwRKGzLvpqYoS4NEbhbx/jV6Z6kyXgJ0IWLZAW20oWmxPwumsqkKr6bWX2NWbGrka6w1e9+iZFBKiBq5zzxJKusCJQtPjuYwjaTGjVTFnixHp9sKnjIEprKyarceG00WzCVdtuI1NpNp8dgemzA6FFt1ESwwELq+rKvECAwEAATANBgkqhkiG9w0BAQUFAAOBgQAokX6HZhhEj7Bfo0Z8ZeoZeYFB8pHrN5A6927cJx17EXWVv0Mwn/+fDgTAhtsN9DB68CFNejox8mM0+KewjsgT4z80YxMHGlpM13z4c8+iMiQcJ7cISScTBaTONOtDqK1WNtci8biNjnLn7+4Z4fw17jlttN0dPHC3fvGywh6TkQ==</o:BinarySecurityToken>
<Signature Id="_0" xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"/>
<Reference URI="#_1">
<Transforms>
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>

</DigestValue>
</Reference>
<Reference URI="#_3">
<Transforms>
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>

</DigestValue>
</Reference>
<Reference URI="#_4">
<Transforms>
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>

</DigestValue>
</Reference>
<Reference URI="#_5">
<Transforms>
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>

</DigestValue>
</Reference>
<Reference URI="#_6">
<Transforms>
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>

</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>

</SignatureValue>
<KeyInfo>
<o:SecurityTokenReference k:TokenType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" xmlns:k="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">
<o:Reference ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" URI="#uuid-5b1de37e-ea76-4f75-b268-ebb63b554c11-1"/>
</o:SecurityTokenReference>
</KeyInfo>
</Signature> <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<Reference URI="#_0">
<Transforms>
<Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>

</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>

</SignatureValue>
<KeyInfo>
<o:SecurityTokenReference>
<o:Reference ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" URI="#uuid-d62ff21f-7e9b-460d-a0ee-d5fad221427d-1"/>
</o:SecurityTokenReference>
</KeyInfo>
</Signature>
</o:Security>
</s:Header>
<s:Body u:Id="_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<e:EncryptedData Id="_2" Type="http://www.w3.org/2001/04/xmlenc#Content" xmlns:e="http://www.w3.org/2001/04/xmlenc#">
<e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
<e:CipherData>
<e:CipherValue>

</e:CipherValue>
</e:CipherData>
</e:EncryptedData>
</s:Body>
</s:Envelope>

How to create a customer from a BP in ECC

Hi Gurus,
I have created a BP customer in SAP and assigned the commission contract role. I made the number range external. This business partner needs to be set up as a customer too. So I used ZD09 account group for the customer and made that number range internal. After I create the BP, how do I create the customer with reference to the BP? I checked the flag in configuration for the BP and customer number to be the same.

Hi
i hope your question is right.
here you are creating one BP with external number ranges and one Customer with internal number ranges.
here roles of these two business persons will be different.
because you have created with an intention that two business partners will do different roles right.
Business partner needs to be set as customer u2013 yes you can do it.
You can copy customer with reference to BP but the result is also same means all the partners with BP and the number will be different by copying it.
regards
balajia

Creating a custom view in WEB UI

Hi Experts,
There is a requirement to create a custom view having few fields of oppurtunity.
Please let me know which is better way of achieving;
1. Copying the standard SAP oppurtunity view of component BP_BPBT.
2. Creating a new custom view with user-defined fields.
This view should be displayed in assignment block of accounts.
Though the SAP standard oppurtunity view is available in BP_HEAD, it is not allowing to display the standard view again in our assignment block.
Could you please let me know the steps to follow for achieving this task. (any of 2 ways)
Regards,
Santosh

Hi Santosh,
You have to place the following code in WD_USAGE_INITIALIZE:
WHEN 'ZBP_BPBT'.
          CALL METHOD iv_usage->bind_context_node
            EXPORTING
              iv_controller_type = cl_bsp_wd_controller=>co_type_component
              iv_name             = iv_usage->usage_name
              iv_target_node_name = 'PARTNER'    " Node of the MAIN component
              iv_node_2_bind      = 'PARTNER'.   " Node of the embedded component
            CALL METHOD iv_usage->bind_context_node
              EXPORTING
                iv_controller_type = cl_bsp_wd_controller=>co_type_component
                iv_target_node_name = 'BUTTONSAVE'    " Node of the MAIN component
                iv_node_2_bind      = 'BUTTONSAVE'.   " Node of the embedded component
And if you want to access the component controller from a view, you can access it by 'me->COMP_CONTROLLER'.
If you are in component controller class, it is just 'me'
Regards
Leon

Business Partners didn't get created from Customer master

T. Code: MDS_LOAD_COCKPIT. Select option Cmr to BP, then in processing, give in customer number (or customer group), select "include values" then give individual number or range of such customers which didn't replicated. Then execute (F8). It will put this process in queuing, so go to next tab "Monitor". Here you can see queue ready for processing, select it, go inside and process (you can also go to smq2). Come back, and see if there is error (red) signal in status column, which means errors. If so, select the line, and click on button "Call PPO". Here you can get the reason/error why replication failed.
Manually, you can give try through t. code: FLBPD1 and give customer number as input.
Check in table KNA1 and BUT000 for verifying if other customers after the tainted one got created as BP or not.
Hope this helps!
I tried FLBPD1 & got the following message:
No business partner could be created for customer 10000578
Message no. CVIC_UI018
Diagnosis
No business partner could be created from the customer selected.
System Response
An error occurred when creating a business partner from the customer selected. This error prevents data from being transferred and saved. This could be due to the following:
Fields have been left blank in the customer that are set as required entry fields for the business partner.
Settings for assigning Customizing values for the customer to the business partner are incorrect.
Procedure
Start the Post Processing Office and check the error message. Make the necessary corrections.
Error Message encountered while using the T. Code MDS_LOAD_COCKPIT:
No transfer of interval for object BU_PARTNER
Message no. NR028
Diagnosis
The last number of the internal interval should be assigned.
Number assignment usually begins in the following call at the start of the interval. However this function is blocked for some number range objects for technical system reasons.
Procedure
If possible extend the interval of the affected number range object. If this is not possible you must reorganize the relevant data and reset the interval status manually.
Please Suggest.
Thanks,
Arpit Kothari

Hello All,
I checked the error with MDS_LOAD_COCKPIT. I found that the VAT Regn no. field was populated for Panama customer. In Panama & Canada, there is no VAT Regn No. I made the field blank in customer master & it created as BP w/o any further issue.
Many Thanks to looking into my issue.
Best Regards,
Arpit Kothari

Issue in creating a custom data model from BP

Hi Team
We have a requirement to create a custom data model by copying data model BP. I have successfully created new data model ZP . I have copied the UI for searching from BP. Issue is when i search a business partner ideally it should not display any entries because i have just created the data model, But it is taking entries from BP and getting displayed. Please let me know how to map data model to search UI. I dont see option USMD_MODEL here

Hi Imran,
actually that is not an issue but a designed feature. I'm afraid that you need to re-think your whole project. The explanations is rather simple:
Data model BP in MDG is a so called Re-Use Area data modell. This means that active data (records that are currently not stored in a change request) are saved in existing SAP ERP data base tables like BUT000 for the business partner master data and LFA1 or KNA1 for Vendor or Customer master data.
If you copy data model BP to ZP you still refer to the same active area. You will always find the same active objects - no matter which data model you are actually using for the user interface. The only difference wil occur for objects being currently processed in a change request. In that case a separation between BP and ZP is possible. But this won't help to solve your issue.
From SAP side I can only recommend not to copy BP but to find a different way of integrating your project needs into BP.
Best regards
Michael

Creating a custom IDoc inbound function module

I have created a custom idoc.I wanted to create a custom IDoc inbound function module, this Function module will provide to launch a BAPI .Tell me how to "create" inbound function module for the custom idoc ?

Goto any standard for the Paramtetres
*" IMPORTING
*"     REFERENCE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     REFERENCE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     REFERENCE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     REFERENCE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     REFERENCE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     REFERENCE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*"     REFERENCE(DOCUMENT_NUMBER) LIKE VBAK-VBELN
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*"      EDI_TEXT STRUCTURE EDIORDTXT1 OPTIONAL
*"      EDI_TEXT_LINES STRUCTURE EDIORDTXT2 OPTIONAL
Do the below configs.
1.Recognise the funcmod as Inbound -BD51
2.Register the Function module in WE57 .
3.we42 Process code .
4. WE20 -PARTNER Profile
I hope it resolves ur Query.
Rgds
Sree M

When linking a BP and Customer, it complains about creating the customer

I am using transaction FLBPD2 to link an existing business partner to an existing FI customer using a business partner role.
It returns the error: Customer 0000200000 already exists
Message no. FLBP155
Diagnosis
You tried to create a business partner in a customer role. The system has been set up in Customizing in such a way that the number selected for the business partner is to be transferred to the customer.
Transaction FLBPD2 is used to link existing BPs to FI customers, not to creating the FI customer! What is causing this?

Hi Lucas and thanks for the reply.
I think my problem is DNS related. I don't know why but the following code stop to work properly when I installed a new OCMS instance with a diferent realm (I was using example.com and now I'm using the same domain as my company, novabase.pt). I put "172.18.88.21 novabase.pt" in the hosts.config file and the only thing that stopped working is the creation of new requests within the SipServlet.
The code:
SipApplicationSession applicationSession =
req.getApplicationSession();
Address to = req.getTo();
Address from =
getSipFactory().createAddress(convertMobile2Address(req.getFrom()));
SipServletRequest request =
getSipFactory().createRequest(applicationSession, "MESSAGE",
from, to);
Object content = req.getContent();
String contentType = req.getContentType();
request.setContent(content, contentType);
from.setDisplayName(req.getFrom().getDisplayName());
request.setHeader("P-Asserted-Identity",
req.getTo().getURI().toString());
System.out.println(request);
request.send();
SipServletResponse response =
req.createResponse(200, "Enderecos trocados!");
response.send();

Create new customer using BAPI BAPI_CUSTOMER_CREATEFROMDATA1

Hi There,
I am trying to create a new customer in SAP through BAPI for demo purpose. The BAPI function I used is BAPI_CUSTOMER_CREATEFROMDATA1. However, the BAPI call requires a reference customer. How can I find a valid reference customer in SAP? Furthermore, is it correct at all to use this BAPI function to create a new customer? Is there any other BAPI function that I can use to do the same stuff? Thanks a lot in advance for your help!
Thanks,
Lei

Hi,
I didn't get which system of SAP are you refering to , but as this forum is for CRM i assume that you want to create customer in CRM.
So for creating a customer in CRM you can use the BAPI,
BAPI_BUPA_CREATE_FROM_DATA
and for getting the reference customer jsut execute the following FM in test enviroment to get the Business Partner no and Business Partner GUID.
CRM_BUPA_CONSUMER_GET_REFERENC
Hope this helps.
Regards
Sidd

Contract partner in ISU to be created as Customer in SD

Similar Messages

Maybe you are looking for